CVE-2026-22610
Angular Template Compiler XSS via SVG href handling.
Is CVE-2026-22610 being exploited?
Not confirmed. CVE-2026-22610 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-22610?
CVE-2026-22610 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-22610?
Yes. A fix has been recorded for CVE-2026-22610. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22610 affect?
CVE-2026-22610 affects Angular (versions < 19.2.18, <20.3.16, <21.0.7, <21.1.0-rc.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22610?
Upgrade to patched Angular versions: 19.2.18, 20.3.16, 21.0.7, or 21.1.0-rc.0
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
XSS in user browsers via unsanitized SVG href/script attributes; could steal data, session tokens, or deface pages.
Patch when possible
- affected>= 21.1.0-next.0 and < 21.1.0-rc.0
- affected>= 21.0.0-next.0 and < 21.0.7
- affected>= 20.0.0-next.0 and < 20.3.16
- affected< 19.2.18
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.