Angular: SSR XSS via Unescaped <template> Content Across DocumentFragment Boundaries in Fallback Raw-Content Elements

Summary

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 untrusted input inside template content nested in fallback raw-content elements such as noscript, iframe, noembed, and noframes. The Domino serializer's fallbackRawContentTags traversal stopped at the DocumentFragment used by template.content, so matching closing tags in xmp, style, script, comments, or text nodes were not escaped. Standard interpolation with comments or text nodes is reachable without relaxed schemas; literal xmp or style requires CUSTOM_ELEMENTS_SCHEMA or NO_ERRORS_SCHEMA, while Renderer2 imperative DOM construction is unconditionally affected. When HTML5 RAWTEXT browser parsing encounters the unescaped closing tag, it exits the fallback container and interprets trailing markup as active DOM elements, enabling arbitrary JavaScript execution. This issue is fixed in versions 20.3.30, 21.2.22, and 22.1.4.

Timeline

1. Sep 10, 2026, 7:04 PM UTCCVE published
2. Sep 10, 2026, 7:19 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: total

3. Sep 10, 2026, 7:20 PM UTCRecord last updated

Affected versions

• angular angular

  through 19.2.25; From 20.0.0 · fixed in 20.3.30; From 21.0.0 · fixed in 21.2.22; From 22.0.0 · fixed in 22.1.4

• @angular/platform-servernpm

  From 22.0.0 · fixed in 22.1.4

• @angular/platform-servernpm

  From 21.0.0 · fixed in 21.2.22

• @angular/platform-servernpm

  From 20.0.0 · fixed in 20.3.30

• @angular/platform-servernpm

  through 19.2.25

References 8