npm package

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

@angular/core 4.1.3 has 8 known vulnerabilities (4 rated high or critical); 20.3.27 fixes all of them. 20.3.27 has 1 known vulnerability of its own, so upgrade to 22.2.3, which has none.

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

Known vulnerabilities
8
4 rated high or critical
Released
May 17, 2017
Latest is 22.2.3
Downloads last week
898
Under 1% of @angular/core downloads
Licence
MIT
Dependencies
None
Resolved by deps.dev

What to upgrade to

22.2.3 is the closest release with no known vulnerabilities that we checked.

  • 4.4.7

    Newest 4.x release. Released Apr 16, 2018.

    8 known vulnerabilities, worst rated warning
  • 20.3.27

    Fixes all 8 known vulnerabilities. Released Jul 29, 2026.

    1 known vulnerability, worst rated warning
  • 22.2.3Upgrade to this

    Latest release. Released Oct 14, 2026.

    No known vulnerabilities

22.2.3 came out on Oct 14, 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 4.1.3

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-69151 on OSV.dev (opens in a new tab)GHSA-jj27-h5hq-8x99

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

    Fixed in 20.3.27. Published Aug 3, 2026.

  2. CriticalCVE-2026-54267 on OSV.dev (opens in a new tab)GHSA-rgjc-h3x7-9mwg

    Angular Client Hydration DOM Clobbering & Response-Cache Poisoning

    Fixed in 20.3.25. Published Jun 15, 2026.

  3. CriticalCVE-2026-27970 on OSV.dev (opens in a new tab)GHSA-prjf-86w9-mfqv

    Angular i18n vulnerable to Cross-Site Scripting

    Fixed in 19.2.19. Published Feb 27, 2026.

  4. CriticalCVE-2026-22610 on OSV.dev (opens in a new tab)GHSA-jrmj-c5cx-3cw6

    Angular has XSS Vulnerability via Unsanitized SVG Script Attributes

    Fixed in 19.2.18. Published Jan 9, 2026.

  5. WarningCVE-2026-88057 on OSV.dev (opens in a new tab)GHSA-hh8m-fm6v-7cvg

    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.

  6. WarningCVE-2026-50557 on OSV.dev (opens in a new tab)GHSA-f3m7-gqxr-g87x

    Angular: Template and Attribute Namespace Sanitization Bypass (XSS)

    Fixed in 19.2.22. Published Jun 15, 2026.

  7. WarningCVE-2026-52725 on OSV.dev (opens in a new tab)GHSA-692r-grfm-v8x7

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

    Fixed in 19.2.23. Published Jun 15, 2026.

  8. WarningCVE-2021-4231 on OSV.dev (opens in a new tab)GHSA-c75v-2vq8-878f

    Angular vulnerable to Cross-site Scripting

    Fixed in 10.2.5. Published May 27, 2022.

Who is still on a vulnerable @angular/core

51% of last week’s 3.4M @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 4.1.3, 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 (didn’t answer) and endoflife.date. Findings from that source may be missing; this page refreshes soon.