Is @angular/core affected by CVE-2026-52725?

npm @angular/core is affected in >=21.0.0-next.0 =22.0.0-next.0 =19.0.0-next.0 =20.0.0-next.0 <20.3.22.

Is CVE-2026-52725 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.4%.

medium

CVE-2026-52725

Q: Is CVE-2026-52725 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.4%.

npm · @angular/core

Summary

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

Severity: medium
EPSS: 0.4% (p33)
Also known as: GHSA-692r-grfm-v8x7
Published: 2026-06-15

References

https://github.com/angular/angular/security/advisories/GHSA-692r-grfm-v8x7
https://github.com/angular/angular/pull/68686
https://github.com/angular/angular/pull/68713

Related advisories

CVE-2026-54267 — high · npm/@angular/core
CVE-2026-88057 — medium · npm/@angular/core
CVE-2026-50557 — medium · npm/@angular/core

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.