CVE-2026-88058
8.6Angular · Angular
A cross-site scripting vulnerability in Angular server-side rendering allows attackers to execute arbitrary JavaScript by manipulating ProcessingInstruction DOM nodes.
Executive summary
A high-severity cross-site scripting vulnerability in Angular server-side rendering allows unauthenticated attackers to achieve arbitrary JavaScript execution in a victim's browser.
Vulnerability
This is a cross-site scripting (CWE-79) flaw where improper neutralization of input occurs during web page generation. The vulnerability exists within the server-side rendering logic, specifically when serializing ProcessingInstruction nodes, and can be triggered by unauthenticated users if application code inserts attacker-controlled data into specific DOM containers.
Business impact
Successful exploitation permits an attacker to execute malicious scripts within the context of the user session, potentially leading to unauthorized data access, session hijacking, or the defacement of web applications. With a CVSS score of 8.6, this vulnerability represents a significant risk to the integrity and confidentiality of user interactions, as it enables client-side code execution without requiring prior authentication.
Remediation
Immediate Action: Update Angular to versions 20.3.30, 21.2.22, or 22.1.4 immediately to apply the necessary output escaping fixes for ProcessingInstruction nodes.
Proactive Monitoring: Review application logs for unusual input patterns involving dynamic DOM insertion or the use of Renderer2 and inject(DOCUMENT) functions that handle untrusted data.
Compensating Controls: Implement a strict Content Security Policy (CSP) that restricts script execution sources, which can mitigate the impact of injected scripts even if the vulnerability is present.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
Given the high CVSS score and the potential for full client-side compromise, security teams should prioritize the deployment of the provided patches across all affected production environments. Because this vulnerability requires specific application-side implementation to be reachable, developers should audit existing code for instances of dynamic DOM manipulation using the vulnerable APIs mentioned in the vendor advisory.
More Angular CVEs all →
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section
Sources
- https://github.com/angular/angular/security/advisories/GHSA-j3r3-mxqp-r2p4
- https://github.com/angular/angular/issues/70146
- https://github.com/angular/angular/commit/73d8bbd27cb46495426d4132975a1355b47ad915
- https://github.com/angular/angular/commit/89b20568dfaee1ec8e0b3bcf1872acdddd2f4fef
- https://github.com/angular/angular/commit/ba3bc47b20b3d12f5eb141ec9c651373ae4d15e8
- https://github.com/angular/domino/commit/04f987dc08ff3736b427f50941adf1722458528f
- https://github.com/angular/angular/releases/tag/v20.3.30
- https://github.com/angular/angular/releases/tag/v21.2.22