Oracle WebLogic Server End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Oracle WebLogic Server versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 11g | 10.3.6 | Jun 1, 2009 | Dec 31, 2018 | Dec 31, 2021 Extended support (ended) |
2794 days past EOL | EOL |
| 12.1 | 12.1.3 | Dec 1, 2011 | Dec 31, 2017 | Dec 31, 2019 Extended support (ended) |
3159 days past EOL | EOL |
| 12.2 | 12.2.1.4.0 | Oct 1, 2015 | Dec 31, 2026 | Dec 31, 2027 Extended support |
128 days remaining | Warning |
| 14.1 | 14.1.2.0.0 | Mar 1, 2020 | Dec 31, 2030 | Dec 31, 2033 Extended support |
1589 days remaining | Active |
| 15 | 15.1.1 | Oct 1, 2025 | Oct 31, 2030 | Oct 31, 2033 Extended support |
1528 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/oracle-weblogic)
Oracle WebLogic Server lifecycle status — the real story
Oracle WebLogic Server's support windows come from Oracle's official Fusion Middleware Lifetime Support Policy (verified against the edition effective April 13, 2026). Oracle publishes these windows to month precision only, so dates on this page use the last day of Oracle's stated month; "end of support" here is the end of Premier Support and "extended support" is the end of paid Extended Support. After Extended Support, Sustaining Support continues indefinitely but delivers no new security fixes — for patching purposes the product is end-of-life.
The line that matters most right now: WebLogic 12.2.x (12.2.1.4) leaves Premier Support in December 2026, with paid Extended Support running only to December 2027. WebLogic 14.1.x (14.1.1 and 14.1.2) has Premier Support to December 2030, and the current release line, WebLogic 15c (15.1.1, released October 2025), runs to October 2030. Note that Oracle's per-patch error-correction windows (MOS KB65053) can end earlier than these lifetime-support dates for individual version lines.
WebLogic's risk profile is not theoretical: CISA added CVE-2026-21962 — a CVSS 10.0, unauthenticated, network-reachable flaw in Oracle HTTP Server and the WebLogic Server Proxy Plug-in, patched in Oracle's January 2026 Critical Patch Update — to the Known Exploited Vulnerabilities catalog on August 24, 2026 with an unusually short August 27 remediation deadline. Only supported versions (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0) received that patch; Oracle's own advisory policy notes that unsupported earlier releases are "likely" affected but are not tested or fixed. Versions 12.1.x and 11g (10.3.x) stopped receiving any security fixes years ago.
Older WebLogic lines footnote: Oracle granted 12.1.3 a limited Extended Support window (Severity 1 and security fixes only) through January 31, 2022 — beyond the December 2019 date in the lifetime table — and no security fixes were ever provided for WebLogic Server Samples. Both exceptions are long past; every 11g and 12.1.x deployment today is unpatched and unpatchable except via migration.
Oracle WebLogic Server release and support pattern
Across the 5 release lines with a published release date, Oracle WebLogic Server has shipped a new line roughly every 4.1 years (median interval). A line typically stays in standard support for about 9.6 years from its release to its standard-support end date.
Of the 5 release lines tracked, 2 are past end of life and 3 are still within support. The newest line, 15, was released October 1, 2025. The next scheduled end of life is 12.2 on December 31, 2026 — 127 days from this build. The longest-supported line currently published is 14.1, to December 31, 2030. Upstream also publishes an extended-support phase for 5 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Oracle WebLogic Server security intelligence
CISA KEV history: Oracle WebLogic Server is named in CISA's Known Exploited Vulnerabilities catalog 13 times, most recently on 2026-08-24, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does Oracle WebLogic Server end of life mean for your organization?
When a version of Oracle WebLogic Server reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Oracle WebLogic Server should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Oracle WebLogic Server reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Oracle WebLogic Server versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Oracle WebLogic Server has 2 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Oracle WebLogic Server is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."