Server-side rendering (SSR) in @angular/platform-server fails to properly escape matching ancestor closing tags when serializing ProcessingInstruction DOM nodes inside fallback raw-content elements. While greater-than characters are escaped, less-than characters remain untouched, allowing a matching closing tag to prematurely terminate containers such as noscript, iframe, noembed, or noframes. This occurs during HTML5 RAWTEXT parsing, causing subsequent sibling elements to be interpreted as live HTML, which enables arbitrary JavaScript execution in the browser. This issue is reachable if application or library code uses `inject(DOCUMENT).createProcessingInstruction()` with attacker-controlled data or performs Renderer2 DOM insertion inside a fallback container.