Vulnerability Database · npm · Package report

angular: vulnerability history, versions and safety

angular is a package in the npm ecosystem. Vulert records 15 vulnerabilities for it across 120 releases, from Jun 2019 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded H3 M9 L3
i
10 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 24 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on angular 1.8.3 i

Updated on 23 Oct 2026

Careful: 1.8.3 has 10 known vulnerabilities, and 10 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 45/100
  • Security Some issues to review
  • Maintenance Deprecated
  • Popularity Key ecosystem project
  • Community Quiet

The registry marks the latest release as deprecated, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.8.3 — affected i
  • Vulnerabilities on record 15 over 6 years · 1 in the last year i
  • Latest disclosure 24 Jun 2026 i
  • Highest CVSS 7.6 i
  • With no published fix 10 i
  • Depended on by 2,805 packages i
  • Stars 58,474 i
  • OpenSSF scorecard 2/10 i
  • Last release 54 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for angular, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.8.3 07 Apr 2022 H2 M5 L3 MIT No Details →
1.8.2 21 Oct 2020 H2 M5 L3 MIT No Details →
1.8.1 05 Oct 2020 H2 M5 L3 MIT No Details →
1.8.0 04 Jun 2020 H2 M5 L3 MIT No Details →
1.7.9 19 Nov 2019 H2 M7 L3 MIT No Details →
1.7.8 11 Mar 2019 H3 M7 L3 MIT No Details →
1.7.7 04 Feb 2019 H3 M7 L3 MIT No Details →
1.7.6 17 Jan 2019 H3 M7 L3 MIT No Details →
1.7.5 04 Oct 2018 H3 M7 L3 MIT No Details →
1.7.4 07 Sep 2018 H3 M7 L3 MIT No Details →
1.7.3 08 Aug 2018 H3 M7 L3 MIT No Details →
1.7.2 12 Jun 2018 H3 M7 L3 MIT No Details →
1.7.1 08 Jun 2018 H3 M7 L3 MIT No Details →
1.7.0 11 May 2018 H3 M7 L3 MIT No Details →
1.7.0-rc.0 19 Apr 2018 H3 M6 L3 MIT No Details →
1.6.10 17 Apr 2018 H3 M6 L3 MIT No Details →
1.6.9 02 Feb 2018 H3 M6 L3 MIT No Details →
1.6.8 21 Dec 2017 H3 M6 L3 MIT No Details →
1.6.7 24 Nov 2017 H3 M6 L3 MIT No Details →
1.6.6 18 Aug 2017 H3 M6 L3 MIT No Details →
1.6.5 03 Jul 2017 H3 M6 L3 MIT No Details →
1.6.4 31 Mar 2017 H3 M6 L3 MIT No Details →
1.6.3 08 Mar 2017 H3 M6 L3 MIT No Details →
1.6.2 07 Feb 2017 H3 M6 L3 MIT No Details →
1.5.11 12 Jan 2017 H3 M7 L3 MIT No Details →
1.6.1 23 Dec 2016 H3 M6 L3 MIT No Details →
1.5.10 16 Dec 2016 H3 M7 L3 MIT No Details →
1.6.0 08 Dec 2016 H3 M6 L3 MIT No Details →
1.6.0-rc.2 24 Nov 2016 H3 M7 L3 MIT No Details →
1.5.9 24 Nov 2016 H3 M7 L3 MIT No Details →
1.6.0-rc.1 21 Nov 2016 H3 M7 L3 MIT No Details →
1.6.0-rc.0 27 Oct 2016 H3 M7 L3 MIT No Details →
1.4.14 11 Oct 2016 H3 M8 L3 MIT No Details →
1.2.32 11 Oct 2016 H2 M8 L2 MIT No Details →
1.2.31 11 Oct 2016 H2 M8 L2 MIT No Details →
1.4.13 10 Oct 2016 H3 M8 L3 MIT No Details →
1.5.8 22 Jul 2016 H3 M7 L3 MIT No Details →
1.2.30 21 Jul 2016 H2 M8 L2 MIT No Details →
1.5.7 15 Jun 2016 H3 M7 L3 MIT No Details →
1.4.12 15 Jun 2016 H3 M8 L3 MIT No Details →
1.5.6 27 May 2016 H3 M7 L3 MIT No Details →
1.4.11 27 May 2016 H3 M8 L3 MIT No Details →
1.5.5 18 Apr 2016 H3 M7 L3 MIT No Details →
1.5.3 25 Mar 2016 H3 M7 L3 MIT No Details →
1.5.2 18 Mar 2016 H3 M7 L3 MIT No Details →
1.4.10 16 Mar 2016 H3 M8 L3 MIT No Details →
1.5.1 16 Mar 2016 H3 M7 L3 MIT No Details →
1.5.0 05 Feb 2016 H3 M7 L3 MIT No Details →
1.5.0-rc.2 28 Jan 2016 H3 M7 L3 MIT No Details →
1.4.9 21 Jan 2016 H3 M8 L3 MIT No Details →
1.5.0-rc.1 15 Jan 2016 H3 M7 L3 MIT No Details →
1.5.0-rc.0 09 Dec 2015 H3 M7 L3 MIT No Details →
1.4.8 20 Nov 2015 H3 M8 L3 MIT No Details →
1.5.0-beta.2 18 Nov 2015 H3 M7 L3 MIT No Details →
1.4.7 29 Sep 2015 H3 M8 L3 MIT No Details →
1.3.20 29 Sep 2015 H3 M8 L3 MIT No Details →
1.2.29 29 Sep 2015 H2 M8 L2 MIT No Details →
1.5.0-beta.0 17 Sep 2015 H3 M8 L3 MIT No Details →
1.4.6 17 Sep 2015 H3 M8 L3 MIT No Details →
1.3.19 16 Sep 2015 H3 M8 L3 MIT No Details →
1.4.5 28 Aug 2015 H3 M8 L3 MIT No Details →
1.3.18 18 Aug 2015 H3 M8 L3 MIT No Details →
1.4.4 13 Aug 2015 H3 M8 L3 MIT No Details →
1.4.3 15 Jul 2015 H3 M8 L3 MIT No Details →
1.3.17 06 Jul 2015 H3 M8 L3 MIT No Details →
1.4.2 06 Jul 2015 H3 M8 L3 MIT No Details →
1.4.1 16 Jun 2015 H3 M8 L3 MIT No Details →
1.3.16 05 Jun 2015 H3 M8 L3 MIT No Details →
1.4.0 27 May 2015 H3 M8 L3 MIT No Details →
1.4.0-rc.2 12 May 2015 H3 M8 L3 MIT No Details →
1.4.0-rc.1 24 Apr 2015 H3 M8 L3 MIT No Details →
1.4.0-rc.0 10 Apr 2015 H3 M8 L3 MIT No Details →
1.3.15 17 Mar 2015 H3 M8 L3 MIT No Details →
1.4.0-beta.6 17 Mar 2015 H3 M8 L3 MIT No Details →
1.4.0-beta.5 24 Feb 2015 H3 M8 L3 MIT No Details →
1.3.14 24 Feb 2015 H3 M8 L3 MIT No Details →
1.4.0-beta.4 09 Feb 2015 H3 M8 L3 MIT No Details →
1.3.13 09 Feb 2015 H3 M8 L3 MIT No Details →
1.3.12 03 Feb 2015 H3 M8 L3 MIT No Details →
1.4.0-beta.3 03 Feb 2015 H3 M8 L3 MIT No Details →
1.3.11 26 Jan 2015 H3 M8 L3 MIT No Details →
1.4.0-beta.2 26 Jan 2015 H3 M8 L3 MIT No Details →
1.4.0-beta.1 20 Jan 2015 H3 M8 L3 MIT No Details →
1.3.10 20 Jan 2015 H3 M8 L3 MIT No Details →
1.3.9 14 Jan 2015 H3 M8 L3 MIT No Details →
1.4.0-beta.0 14 Jan 2015 H3 M8 L3 MIT No Details →
1.3.8 19 Dec 2014 H3 M8 L3 MIT No Details →
1.2.28 15 Dec 2014 H2 M8 L2 MIT No Details →
1.3.7 15 Dec 2014 H3 M8 L3 MIT No Details →
1.3.6 09 Dec 2014 H3 M8 L3 MIT No Details →
1.3.5 02 Dec 2014 H3 M8 L3 MIT No Details →
1.3.4 24 Nov 2014 H3 M8 L3 MIT No Details →
1.2.27 20 Nov 2014 H2 M8 L2 MIT No Details →
1.3.4-build.3588 20 Nov 2014 H3 M8 L3 MIT No Details →
1.3.3 18 Nov 2014 H3 M8 L3 MIT No Details →
1.3.2 07 Nov 2014 H3 M8 L3 MIT No Details →
1.3.1 31 Oct 2014 H3 M8 L3 MIT No Details →
1.3.0 13 Oct 2014 H3 M8 L3 MIT No Details →
1.3.0-rc.5 08 Oct 2014 H2 M8 L3 MIT No Details →
1.2.23 31 Aug 2014 H2 M8 L2 MIT No Details →
1.2.22 31 Aug 2014 H2 M8 L2 — No Details →
1.2.21 11 Aug 2014 H2 M8 L2 — No Details →
1.2.20 11 Aug 2014 H2 M8 L2 — No Details →
1.2.19 02 Jul 2014 H2 M8 L2 — No Details →
1.2.18 19 Jun 2014 H2 M8 L2 — No Details →
1.2.17 19 Jun 2014 H2 M8 L2 — No Details →
1.2.16 18 Apr 2014 H2 M8 L2 — No Details →
1.2.15 26 Mar 2014 H2 M8 L2 — No Details →
1.2.14 26 Mar 2014 H2 M8 L2 — No Details →
1.2.13 26 Mar 2014 H2 M8 L2 — No Details →
1.2.12 26 Mar 2014 H2 M8 L2 — No Details →
1.2.11 26 Mar 2014 H2 M8 L2 — No Details →
1.2.10 27 Jan 2014 H2 M8 L2 — No Details →
1.2.9 27 Jan 2014 H2 M8 L2 — No Details →
1.2.8 27 Jan 2014 H2 M8 L2 — No Details →
1.2.7 07 Jan 2014 H2 M8 L2 — No Details →
1.2.6 07 Jan 2014 H2 M8 L2 — No Details →
1.2.5 07 Jan 2014 H2 M8 L2 — No Details →
1.2.4 07 Jan 2014 H2 M8 L2 — No Details →
1.2.3 07 Jan 2014 H2 M8 L2 — No Details →

The newest 120 of 144 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2020 3
  • 2022 2
  • 2023 3
  • 2024 3
  • 2025 1
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 15 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for angular

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About angular

Is angular safe to use?

Vulert records 15 vulnerabilities for angular in npm: 0 critical, 3 high, 9 medium and 3 low. 10 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is angular's Vulert package health score?

Vulert scores angular 45/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of angular affected?

Yes. 1.8.3, the version you would install today, has 10 known vulnerabilities, and 10 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of angular should I use?

1.8.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does angular have?

15 vulnerabilities are recorded for angular in the npm ecosystem: 0 critical, 3 high, 9 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new angular vulnerabilities disclosed?

1 vulnerability was recorded for angular in the last 12 months, and the oldest entry in this database dates to 27 Jun 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of angular are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor angular for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the angular version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.