Angular: SSR XSS via Unescaped Processing Instruction (<?...?>) Nodes in Fallback Raw-Content Elements
angular
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @angular/platform-server npm |
|
|
angular
| Product | Affected | Fixed in |
|---|---|---|
| @angular/platform-server npm |
|
|
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.30, 21.2.22, and 22.1.4, Angular server-side rendering (SSR) in @angular/platform-server serializes ProcessingInstruction DOM nodes inside fallback raw-content elements without escaping matching ancestor closing tags. ProcessingInstruction data escaped greater-than characters but left less-than characters untouched and did not inspect fallback ancestors, so data such as a matching closing tag prematurely terminates noscript, iframe, noembed, or noframes containers. The vulnerable nodes cannot be authored through standard Angular templates; reachability requires application or library code using inject(DOCUMENT).createProcessingInstruction with attacker-controlled data or Renderer2 DOM insertion inside a fallback container. In HTML5 RAWTEXT parsing, the premature close causes subsequent sibling elements to be interpreted as live HTML and enables arbitrary JavaScript execution in a victim's browser. This issue is fixed in versions 20.3.30, 21.2.22, and 22.1.4.
From the CVE record · GitHub_M
Angular SSR in @angular/platform-server fails to escape matching closing tags when serializing ProcessingInstruction nodes inside fallback raw-content elements. If application or library code inserts attacker-controlled ProcessingInstruction data into such a container, the rendered HTML can execute arbitrary JavaScript in a victim's browser. These nodes cannot be authored through standard Angular templates.
Teams using npm @angular/platform-server versions >=22.0.0 <22.1.4, >=21.0.0 <21.2.22, >=20.0.0 <20.3.30, or <=19.2.25 should check their applications.