Java 11 is a long-term support release, and Oracle's roadmap lists Premier Support as ended in September 2023 with Extended Support until January 2032. So it is past the first phase but not retired. Whether you get fixes depends on your vendor build and support terms.
The dates on Oracle's page
Oracle's Java SE support roadmap lists Java 11 (LTS) with general availability in September 2018, Premier Support until September 2023, and Extended Support until January 2032. Sustaining Support is listed as indefinite. The page also states that Oracle intends to ship future LTS releases every two years, and names Java 29 in September 2027 as the next planned LTS.
Two ideas help here. First, LTS means the release gets a longer support window than a normal feature release, not that it never expires. Second, the roadmap covers Oracle's products. A different vendor's Java 11 build has its own dates, which you must read from that vendor.
Why teams stay on Java 11
Java 11 is a common landing spot because it sat between the Java 8 era and the newer module-heavy releases. Upgrading from it can be quiet or painful depending on what the code touches: reflection into JDK internals, removed APIs, and older frameworks that assume specific runtime behavior. Read Java 17 strong encapsulation and add-opens before you plan a jump, because the same class of issue applies on the way up.
A short decision guide
- You hold a support contract and apply updates. Record the runtime as Extended, note the end date, and set a review date well ahead of it.
- You use a vendor build with a published free update stream. Record the vendor's stated end date from their own page and the date you checked it.
- You cannot show where updates come from. Record it as unsupported for patching and put an upgrade or isolation plan in the register.
If none of the three fits, the honest status is unknown. Unknown is a valid inventory value and a useful trigger for investigation.
Fields that make the record useful
| Field | Example value | Why |
|---|---|---|
| Runtime | Java 11, vendor and build | Dates are vendor specific |
| Phase | Extended | Drives urgency |
| End date | As stated on the vendor page | Drives the calendar |
| Source and check date | Page and 19 October 2026 | Proves you looked |
| Owner | Team name | Someone has to act |
| Exposure | Internal service | Orders the work |
Keep the check date. Roadmaps change, and a date you verified a year ago may no longer be the one on the page. For more on keeping these from going stale, see how to track software support windows without spreadsheet rot.
Try it yourself
Click through it at your own pace, or open it full screen. Watch how findings are grouped and prioritized, then think about where a runtime lifecycle flag would sit in that list.
Where Safeguard fits
Safeguard's SBOM and dependency scanning gives you the component inventory to hang these fields on, and its policies can express rules about what your team accepts. A free scan is available at gold.safeguard.sh/scan.
Quick check
Is Java 11 still receiving security updates?
From Oracle, under Extended Support terms until the listed date. From other vendors, only as their own pages state. Check the build you actually run.
Is LTS the same as supported forever?
No. LTS gives a longer window, and every window ends.
Sources
Last reviewed: 19 October 2026.
