ANGULAR COVERAGE
Angular 18 and 19 are end of life. Your patching does not have to be.
OSSeva provides security patches for Angular 18 and 19 after the Angular team stopped fixing them, so a production application keeps its framework version while the upgrade is planned. AngularJS 1.8 is covered on its own page. Other versions are assessed case by case.
Reply within 1 business day ยท No commitment ยท or book a 15-minute call
Last reviewed
Trusted globally by enterprises





Why now
Angular 19 left support on 19 May 2026, Angular 18 on 21 November 2025
endoflife.date lists Angular 19 with an end of life of 2026-05-19 and Angular 18 with 2025-11-21, and angular.dev states that versions 2 to 19 are no longer supported. The last releases were 19.2.25 and 18.2.14.
Angular 20 leaves long-term support on 28 November 2026
The angular.dev support table gives 28 November 2026 as the end of long-term support for Angular 20. A team that moves from 18 or 19 to 20 reaches the same decision within days.
An upgrade is a chain of major versions
angular.dev says ng update works within one major version, so going from Angular 18 to 22 is four updates in a row, each with its own Node.js and TypeScript range on the angular.dev version compatibility page. Patching the version you run removes the deadline from that project.
AngularJS (1.x) is a separate product and ended earlier
AngularJS support ended on 31 December 2021 and its last release is 1.8.3. It has its own page with the post-end-of-life CVEs and the options.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 18(Community EOL 21 Nov 2025 (last release 18.2.14)) | EOL | Clean |
| 19(Community EOL 19 May 2026 (last release 19.2.25)) | EOL | Clean |
| 20(Long-term support only; community EOL 28 Nov 2026. Assessed case by case.) | Current | Clean |
| 21(Long-term support only; community EOL Jun 2027. Supported upstream.) | Current | Clean |
| 22(Active support; community EOL 30 Jun 2028. Supported upstream.) | Current | Clean |
Running a Angular version or build not listed here?
What you get
Three tiers โ pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Security patches for Angular 18 and 19 after end of life.
- Backported security fixes for Angular 18 and 19
- Critical CVEs fixed within 48 hours, High within 7 days
- Signed artifacts (GPG + Sigstore)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus compliance documentation and upgrade planning.
- Everything in Patch
- SOC 2 / HIPAA attestation package
- Angular upgrade path assessment
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.
- Everything in Assure
- 24/7 application and runtime monitoring
- 15-minute P1 incident response SLA
- Named senior engineer on your account
All tiers priced per cluster/application โ not per core.
Compliance library
Which Angular versions does OSSeva patch?
Angular 18 and 19 after end of life. Other versions are assessed case by case. AngularJS 1.8 has its own page at /eol/angularjs.
How fast are Angular vulnerabilities patched?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.
Is Angular 19 end of life?
Yes. endoflife.date lists 19 May 2026 as its end of life, and angular.dev states that versions 2 to 19 are no longer supported. The last release was 19.2.25.
How is OSSeva Angular support priced?
It is priced per application, like the rest of OSSeva. Request a quote and a senior engineer replies within 1 business day.
Get a quote
Ready to get Angular patched and supported?
Tell us your Angular versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?