CVE-2026-22610: Angular has XSS Vulnerability via Unsanitized SVG Script Attributes
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.
Security readout for executives and security teams
Plain-English summary
Angular versions before the listed fixes can mishandle certain SVG script link attributes, creating an XSS risk. In business terms, a vulnerable app could let attacker-controlled content run in a user’s browser if the required conditions are met. The source bundle provides fixes but no evidence of active exploitation.
Executive priority
Treat this as a high-priority dependency upgrade for internet-facing Angular applications. The issue can affect browser-side trust and data integrity, but current evidence in the bundle does not support emergency active-exploitation handling.
Technical view
CVE-2026-22610 is a CWE-79 issue in Angular’s Template Compiler sanitization schema. It fails to treat SVG <script> href and xlink:href attributes as Resource URL contexts. Fixed versions are 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0.
Likely exposure
Exposure is likely limited to applications built with affected Angular versions, especially where SVG-related template content or attacker-influenced values may be rendered. The bundle references Siemens advisories, but does not provide enough detail here to name specific Siemens product exposure.
Exploitation context
The CVSS vector indicates network access, low attack complexity, low privileges, and user interaction. The source bundle marks KEV as false and provides no cited evidence of in-the-wild exploitation, so active exploitation should not be assumed.
Researcher notes
Focus analysis on Angular compiler sanitization behavior for SVG script href and xlink:href attributes. Avoid assuming exploitability in every Angular app; practical exposure depends on version, template usage, and attacker control of rendered data.
Mitigation direction
Upgrade Angular to 19.2.18, 20.3.16, 21.0.7, 21.1.0-rc.0, or later.
Prioritize public-facing Angular applications and apps handling untrusted user content.
Check Angular’s advisory and vendor guidance for any version-specific upgrade notes.
Track referenced Siemens advisories if your environment uses Siemens products.
Retest affected user-facing workflows after upgrading Angular.
Validation and detection
Inventory Angular versions from dependency manifests, lockfiles, and SBOMs.
Compare each application against the affected version ranges in the CVE record.
Confirm CI builds use the patched Angular compiler version.
Review routes or components that render SVG or user-controlled template data.
Verify no production deployment still references vulnerable Angular builds.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.