To tell whether Jenkins is out of date, compare your core version to the current LTS line, check that your Java version is still supported, and read plugin warnings in the plugin manager. A new LTS arrives every 12 weeks, so a controller a year old is about four lines behind.
Four checks
- Core version. The footer of any Jenkins page shows it. Compare it with the LTS lines in the upgrade guide. Recent ones listed there are 2.541.x, 2.555.x, 2.568.x and 2.580.x.
- Java version. Supported today are 21 and 25. Java 17 is unsupported, with 2.541.3 as its final LTS.
- Plugin warnings. The plugin manager shows warning metadata for vulnerable plugins, including some with no fix.
- Plugin updates. The Updates tab lists available versions. The Health Score is also shown, and it reflects the latest data rather than your installed version.
A simple gap table
| Finding | Meaning | First action |
|---|---|---|
| Core within the current or previous LTS line | Close to current | Schedule routine updates |
| Several LTS lines behind | Missing many fixes | Read each upgrade guide, test on a copy |
| Java unsupported | Newer Jenkins will not start | Plan Java and core together |
| Plugin with an advisory and no fix | Open exposure | Apply workaround or remove |
| Agents on old Java | Agent connection may fail after upgrade | Update agents too |
Note the arithmetic in the opening paragraph is an estimate from the 12 week cadence, not a measurement of your instance. Check your exact version.
What "out of date" does not tell you
Age is a signal, not a verdict. A recent controller can still have a risky plugin or a weak authorization setup. An older one that is isolated, patched where it counts, and watched may carry less risk than a fresh install with open permissions. Use age to prioritize, then look at exposure: who can reach it, what it can deploy to, and what secrets it holds.
What to do with the answer
- Close: subscribe to advisories and keep a routine.
- Behind: build a staging copy and upgrade in order, following the step by step post at upgrade Jenkins LTS.
- Far behind: consider whether to upgrade or migrate. The inventory post at what to inventory before migrating helps with that choice.
Try it yourself
The demo shows how reachability analysis cuts a long finding list down to what can actually be reached, a useful way to prioritize an old estate.
Click through it at your own pace, or open it full screen.
Where Safeguard fits
Safeguard provides reachability analysis and dependency scanning to help rank what to fix first. Try the free scan.
Quick check
How often is a Jenkins LTS selected?
Every 12 weeks, from the regular release stream.
Is Java 17 still supported by Jenkins?
No. The support policy lists it as unsupported, with 2.541.3 as its final LTS.
Sources
- Jenkins: LTS upgrade guide
- Jenkins: Java support policy
- Jenkins: Installing on Linux
- Jenkins: Managing plugins
- Jenkins: Vulnerabilities in plugins
Last reviewed: 19 October 2026.
