Angular vulnerabilities: known CVEs & security history
Google · Web / Framework · 6 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Angular release lines — 6 in total. A CVE here doesn't mean your version is affected — check Angular's current status and the safe version to run.
Known Angular CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-27970 | medium | 6.1 | 0% | 2026 |
| CVE-2026-22610 | medium | 6.1 | 0% | 2026 |
| CVE-2025-66412 | medium | 5.4 | 0% | 2025 |
| CVE-2025-61261 | medium | 5.4 | 0% | 2025 |
| CVE-2026-41423 | medium | 5.3 | 0% | 2026 |
| CVE-2021-4231 | low | 3.5 | 1% | 2022 |
Is my Angular version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Angular version → · Monitor Angular for new CVEs →
Angular vulnerabilities — frequently asked
How many known vulnerabilities does Angular have?
IsItPatched tracks 6 CVEs for Angular. 0 are critical-severity and 0 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Angular have any actively-exploited vulnerabilities?
None of Angular's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Angular vulnerability?
Among tracked issues, CVE-2026-27970 (MEDIUM, CVSS 6.1) ranks highest — a Cross-site scripting (XSS) weakness.
Is Angular safe to use?
It depends on the version. The latest supported Angular release (22.0.1) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Angular security status · Angular end-of-life · actively-exploited CVEs. Always verify against Google's advisories — see our disclaimer.