npm package

@angular/core 12.0.0 vulnerabilities, and the version that fixes all of them

@angular/core 12.0.0 has 7 known vulnerabilities (4 rated high or critical); 20.3.28 fixes all of them. Angular 12 reached end of life on Nov 12, 2022 and gets no more security fixes. Move to Angular 22.

npm (opens in a new tab) describes it as “Angular - the core framework”

Known vulnerabilities
7
4 rated high or critical
Released
May 12, 2021
Latest is 22.2.3
Downloads last week
1.1K
Under 1% of @angular/core downloads
Angular 12 support
End of life
Since Nov 12, 2022
Licence
MIT
Pulls in
1 package
Resolved by deps.dev

What to upgrade to

20.3.28 is the closest release with no known vulnerabilities.

  • 12.2.17

    Newest 12.x release. Released Nov 22, 2022.

    7 known vulnerabilities, worst rated warning
  • 20.3.28Upgrade to this

    Fixes all 7 known vulnerabilities. Released Aug 13, 2026.

    No known vulnerabilities
  • 22.2.3

    Latest release. Released Oct 14, 2026.

    No known vulnerabilities

20.3.28 came out on Aug 13, 2026. A coding agent trained before then doesn’t know it exists, so it may suggest an older release. AI knowledge cutoff dates

Hand the fix to your coding agent

One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.

Findings

Every advisory for @angular/core 12.0.0

Known exploited first (CISA KEV), then by how likely they are to be exploited (FIRST EPSS), then by severity. Each id links to its OSV.dev record.

  1. CriticalCVE-2026-27970 on OSV.dev (opens in a new tab)GHSA-prjf-86w9-mfqvEPSS: top 62%

    Angular i18n vulnerable to Cross-Site Scripting

    Fixed in 19.2.19. Published Feb 27, 2026.

  2. CriticalCVE-2026-22610 on OSV.dev (opens in a new tab)GHSA-jrmj-c5cx-3cw6EPSS: top 64%

    Angular has XSS Vulnerability via Unsanitized SVG Script Attributes

    Fixed in 19.2.18. Published Jan 9, 2026.

  3. WarningCVE-2026-52725 on OSV.dev (opens in a new tab)GHSA-692r-grfm-v8x7EPSS: top 68%

    @angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)

    Fixed in 19.2.23. Published Jun 15, 2026.

  4. WarningCVE-2026-88057 on OSV.dev (opens in a new tab)GHSA-hh8m-fm6v-7cvgEPSS: top 71%

    Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler

    Fixed in 20.3.28. Published Sep 10, 2026.

  5. WarningCVE-2026-50557 on OSV.dev (opens in a new tab)GHSA-f3m7-gqxr-g87xEPSS: top 74%

    Angular: Template and Attribute Namespace Sanitization Bypass (XSS)

    Fixed in 19.2.22. Published Jun 15, 2026.

  6. CriticalCVE-2026-69151 on OSV.dev (opens in a new tab)GHSA-jj27-h5hq-8x99EPSS: top 76%

    Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes

    Fixed in 20.3.27. Published Aug 3, 2026.

  7. CriticalCVE-2026-54267 on OSV.dev (opens in a new tab)GHSA-rgjc-h3x7-9mwgEPSS: top 78%

    Angular Client Hydration DOM Clobbering & Response-Cache Poisoning

    Fixed in 20.3.25. Published Jun 15, 2026.

Who is still on a vulnerable @angular/core

54% of last week’s 6.2M @angular/core downloads went to versions with known vulnerabilities.

From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover 98% of downloads.

Is @angular/core the only one?

Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.

Check your whole repo

How this page is checked

StackPrism asks OSV.dev which advisories affect exactly @angular/core 12.0.0, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm, support dates from endoflife.date. No AI writes this page: every sentence comes from that data, refreshed every few hours.

Last checked against npm, OSV.dev, deps.dev, CISA KEV, FIRST EPSS and endoflife.date.