SAP NetWeaver End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all SAP NetWeaver versions. Dates read at the vendor's own lifecycle pages (pages.community.sap.com). Updated at every deploy.
SAP NetWeaver 7.5 (AS ABAP / AS Java) is supported until December 31, 2027, its end-of-support date. It is also the next SAP NetWeaver version to reach end of life. 3 of 4 tracked SAP NetWeaver versions are past end of life; the most recent to reach it, 7.4, did so on December 31, 2020. The full SAP NetWeaver lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 7.1x | 7.1x | — | Dec 31, 2020 | — | 2110 days past EOL | EOL |
| 7.3 / 7.31 (7.03) | 7.31 | — | Dec 31, 2020 | — | 2110 days past EOL | EOL |
| 7.4 | 7.4 | — | Dec 31, 2020 | — | 2110 days past EOL | EOL |
| 7.5 (AS ABAP / AS Java) | 7.5 | — | Dec 31, 2027 | Dec 31, 2030 Extended support |
446 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/sap-netweaver)
SAP NetWeaver lifecycle status — the real story
SAP NetWeaver is the application server platform (AS ABAP and AS Java) under SAP Business Suite 7 and SAP ECC. SAP's public SAP NetWeaver 7.5 Maintenance Strategy page states that "SAP NetWeaver 7.5 will be supported in mainstream maintenance until end of 2027" and that "Extended maintenance for SAP NetWeaver 7.5 will be offered until end of 2030 at the same price and conditions like with SAP Business Suite 7", that is at a premium of two percentage points on the maintenance basis. SAP publishes these as year ends; the dates here read "end of 2027" as December 31, 2027, the same reading used for SAP ECC.
The same page says earlier releases "such as 7.4, 7.3, 7.31 and 7.1x will run out of mainstream maintenance end of 2020" and that "Extended maintenance will not be offered for these versions", with one carve-out: "SAP will, however, support the Application Server ABAP 7.4 and 7.31 (which is identical to 7.03) to fulfill the maintenance commitment for the ABAP-based parts of SAP Business Suite 7". An AS ABAP 7.4 or 7.31 system that is part of a Business Suite 7 landscape is therefore covered by the suite's timeline, not by the 2020 date shown for the full NetWeaver release.
Per-component detail (the Product Availability Matrix and SAP Note 1648480) is behind an SAP login and is not reproduced here. NetWeaver is the most exploited SAP product in CISA's Known Exploited Vulnerabilities catalog: ten entries from CVE-2010-5326 (Invoker Servlet) to CVE-2025-31324 and CVE-2025-42999 (Visual Composer, both used in ransomware campaigns), plus CVE-2022-22536 (ICMAD) filed under "Multiple Products".
SAP NetWeaver release and support pattern
Of the 4 release lines tracked, 3 are past end of life and 1 is still within support. The next scheduled end of life is 7.5 on December 31, 2027 — 446 days from this build. Upstream also publishes an extended-support phase for 1 line, 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.
SAP NetWeaver security intelligence
CISA KEV history: SAP NetWeaver is named in CISA's Known Exploited Vulnerabilities catalog 11 times, most recently on 2025-05-15, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does SAP NetWeaver end of life mean for your organization?
When a version of SAP NetWeaver 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL SAP NetWeaver 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 SAP NetWeaver 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 SAP NetWeaver versions. This is a bridge, not a permanent solution — plan your migration in parallel.
SAP NetWeaver has 3 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 SAP NetWeaver 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."