End of life

AngularJS end of life

AngularJS is end of life. Google's long-term support ended on 31 December 2021, and the last release, 1.8.3 of 7 April 2022, only updated package READMEs. The GitHub repository was archived on 12 April 2024, so new flaws such as CVE-2026-11998 get no upstream fix. You can rewrite in Angular, or keep AngularJS 1.8 patched by a third party.

What now

Which vendors provide AngularJS 1.8 security patches now that support has ended?

Angular extended support

Only your email is required · An engineer replies within 1 business day · No commitment

End of life
31 December 2021
Released
Jun 2020
Final release
1.8.3 (7 April 2022)
Successor
Angular 21 or 22

Date published by Angular blog: Discontinued Long Term Support for AngularJS. We do not publish a lifecycle date we cannot source. Dates checked on the AngularJS project's announcement, repository and endoflife.date on 19 November 2026.

Last reviewed

AngularJS versions: release and end-of-life dates

AngularJS release and end-of-life dates
VersionReleasedEnd of lifeStatus
AngularJS 1.8 (this page)4 Jun 202031 December 2021End of life

End-of-life dates are published by each project and checked against endoflife.date.

What actually stops on 31 December 2021

  • Security and bug fixes on every 1.x line. The Angular team's announcement of 11 January 2022 ended long-term support, which it had extended to 31 December 2021 because of the pandemic.
  • Any release at all after 1.8.3. That release, "ultimate-farewell" in the changelog, only updated the README files on npm.
  • Upstream review of pull requests and issues. The angular/angular.js repository was archived and is read-only; its last push was on 12 April 2024.
  • Fixes for vulnerabilities published afterwards. The CVE-2026-11998 record says the project was already end of life and will not receive updates to address it.

What actually breaks in the upgrade

Angular is the named successor, and it is a rewrite

The Angular team's announcement points teams to Angular, and the two are different frameworks. Controllers, scopes, directives and templates do not carry over, so the move is a rewrite of the front end rather than a version bump. Angular 21 is supported to June 2027 and Angular 22 to June 2028, per angular.dev. Angular end of life dates.

The npm packages and CDN links keep working, unpatched

The announcement says the AngularJS npm packages stay on npm and bower marked as deprecated, and the CDN links stay active. A site that loads AngularJS from a CDN therefore keeps loading the unpatched file. Nothing breaks, so nothing prompts a change.

AngularJS Material is archived too

The same announcement lists AngularJS Material and bower-material among the repositories archived. If your interface uses it, the component library has no maintainer either, so the rewrite scope includes it.

What actually ended in 2021 and 2022

AngularJS did not stop on one day. The Angular team set the end of long-term support at 31 December 2021 (extended from an earlier date because of the pandemic) and announced the end on 11 January 2022. One more release followed: 1.8.3 on 7 April 2022, which the changelog calls "ultimate-farewell" and describes as a final release to update the README files on npm. So the code is that of 1.8.2 from October 2020.

The repository was archived and its last push was on 12 April 2024. The project's own pull requests and issue tracker are closed, so a fix for a new flaw cannot be contributed upstream and picked up from there. Every fix for AngularJS now comes from whoever sells it to you.

The most recent vulnerability shows what that means in practice. CVE-2026-11998, published on 24 June 2026, is a bypass in AngularJS's strict contextual escaping for resource URLs: a flaw in how whole URLs are matched against regular-expression entries can produce partial matches, which allows an unsafe resource URL to be trusted. If your application has regular-expression entries in its resource URL allowlist (the trusted resource URL list in the $sce services), review them whether or not you patch. The CVE record states plainly that the project is end of life and will not issue a fix.

Two practical consequences follow from the announcement. The CDN links and npm packages remain, so nothing fails when the code stops being maintained. And the 1.8 line is the only one with a long tail of third-party coverage: HeroDevs lists 1.4.x, 1.5.x and 1.8.x on its own page, and OSSeva patches 1.8. An application on a lower 1.x line should check which of those it can move to first, and ask for a version coverage check if it cannot.

AngularJS CVEs published after end of life

Nine CVEs published since 2022 list AngularJS 1.8.3, the final release, as affected, and none has an upstream fix. Each row below was checked on 19 November 2026 in the CVE record (cveawg.mitre.org) and in the GitHub advisory for the npm package angular, and both agree on the affected versions and on the absence of a patched version.

CVEWhat it isCVSS 3.1Affected AngularJSPublishedUpstream fix
CVE-2026-11998XSS: bypass of strict contextual escaping for resource URLsHigh (7.6)1.2.0-rc.3 and later, including 1.8.3Jun 2026None
CVE-2025-0716Improper sanitization of the SVG <image> elementMedium (4.8)Includes 1.8.3Apr 2025None
CVE-2024-8373Image source restriction bypass via the <source> elementMedium (4.8)Includes 1.8.3Sep 2024None
CVE-2024-8372Image source restriction bypass via the srcset attributeMedium (4.8)1.3.0-rc.4 and later, including 1.8.3Sep 2024None
CVE-2024-21490Denial of service: super-linear regular expression in ng-srcsetHigh (7.5)1.3.0 and later, including 1.8.3Feb 2024None
CVE-2023-26116Denial of service via the angular.copy() utilityMedium (5.3)Includes 1.8.3Mar 2023None
CVE-2023-26117Denial of service via the $resource serviceMedium (5.3)Includes 1.8.3Mar 2023None
CVE-2023-26118Denial of service via the <input type="url"> elementMedium (5.3)Includes 1.8.3Mar 2023None
CVE-2022-25844Denial of service via a custom locale rule (posPre)Medium (5.3)1.7.0 and later, including 1.8.3May 2022None

Sources: cveawg.mitre.org CVE records and GitHub security advisories GHSA-7x27-g8rg-x87w, GHSA-j58c-ww9w-pwp5, GHSA-mqm9-c95h-x2p6, GHSA-m9gf-397r-hwpg, GHSA-4w4v-5hc9-xrr2, GHSA-2vrf-hf26-jrp5, GHSA-2qqx-w9hr-q5gx, GHSA-qwqh-hm9m-p5hr and GHSA-m2h2-264f-f486, checked 19 November 2026. A CVE whose record and advisory disagree on the score is left out. This is a list of CVEs that were cross-checked, not every AngularJS issue.

Who patches AngularJS after end of life?

The AngularJS project does not. HeroDevs sells AngularJS patches and states its coverage on its own page, read on 19 November 2026. OSSeva patches AngularJS 1.8.

Facts from each provider's own page, read on 19 November 2026.

ProviderAngularJS versions the page listsFix timing the page states
HeroDevs (NES for AngularJS)1.4.x, 1.5.x and 1.8.xSecurity-related and application-breaking issues resolved immediately, same day if possible
OSSeva1.8. Other lines case by caseCritical within 48 hours, High within 7 days

How we compared: the HeroDevs row uses only its own AngularJS page, read on 19 November 2026. The two timing statements are different measures (a response commitment and a patch window). Where HeroDevs is the better fit: it lists 1.4.x and 1.5.x, which OSSeva assesses case by case. We did not read other providers' pages and have not listed them.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Rewrite in Angular 21 or 22Move to the supported successor, component by component or as a new front end behind the same API.Scales with application size and test coverageEngineering timeThe long-term answer.
Keep AngularJS 1.8 patchedBackported fixes for the published AngularJS CVEs and new ones: Critical within 48 hours, High within 7 days.Starts from your current versionSubscription, priced per applicationFor applications that cannot be rewritten this year, or that sit behind a release freeze or vendor certification.
Stay unpatchedEvery CVE published since 2022 stays open, including a 7.6 XSS in the resource URL allowlist.NoneZero nowAngularJS runs in the browser of every user of the site. A poor place to carry risk.

What OSSeva does for AngularJS 1.8

OSSeva patches this line

OSSeva patches AngularJS 1.8, the last line, after end of life. Other AngularJS lines are assessed case by case through a version coverage check.

Angular extended support

What your auditor will say

PCI DSS 4.0

Requirement 6.3.3. Payment pages that load AngularJS need patched components or a documented compensating control.

SOC 2

CC7.1. Auditors look for evidence that components in production receive security fixes.

Compliance library Angular end of life dates for every version

Questions

AngularJS 1.8: common questions

Book a 15-minute call

Is AngularJS end of life?

Yes. Long-term support ended on 31 December 2021, and the Angular team announced it on 11 January 2022. The last release was 1.8.3, on 7 April 2022.

What is the last AngularJS version?

1.8.3, released on 7 April 2022 and called "ultimate-farewell" in the changelog. It only updated the package README files on npm, so the code is the same as 1.8.2.

Is AngularJS still safe to use?

Not without patches. Nine CVEs published since 2022 and listed below affect 1.8.3, and the project will not fix any of them, so an unpatched AngularJS 1.8 application carries all of them.

Who provides AngularJS support after end of life?

Not the AngularJS project, which archived its repository. HeroDevs lists NES for AngularJS 1.4.x, 1.5.x and 1.8.x on its own page, and OSSeva patches AngularJS 1.8.

Should I migrate AngularJS to Angular?

Eventually, yes: Angular is the successor the AngularJS team names, and Angular 22 is supported to June 2028. But it is a rewrite, so many teams keep AngularJS patched while they plan it.

Is the AngularJS CDN still available?

Yes. The end-of-life announcement says the CDN links stay active and the npm packages stay available, marked as deprecated. Availability is not support: the files are not patched.

Get a quote

Still running AngularJS 1.8?

Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call