llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · @angular/platform-server

GHSA-VPX6-8PJR-4G3V

Angular SSR: Missing Fallback Raw-Content Serialization Escaping leads to Cross-Site Scripting (XSS)

Parche disponible
Descargar PNG JSON
CVSS
—
high
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche3 versionesPrimer parche a -18 d de la divulgación
Exposición108 dDesde la divulgación, 3 ago 2026, 11:14 a. m.
Detección105 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche 22.0.7
Parche 20.3.27 +1
Monitoreo
Detectada
16 jul 26
29 jul 26
3 ago 26
17 nov 26
19 nov 26
16 jul 26
17 ago 26
17 sept 26
19 oct 26
19 nov 26
FechaFaseEventoDetalle
Remediación Parche 22.0.7 @angular/platform-server · -18 d desde divulgación
Remediación Parche 20.3.27 @angular/platform-server · -5 d desde divulgación
Remediación Parche 21.2.19 @angular/platform-server · -5 d desde divulgación
Divulgación Publicada GHSA-VPX6-8PJR-4G3V divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

A Cross-Site Scripting (XSS) vulnerability exists in `@angular/platform-server`'s DOM emulation dependency (`domino`) when serializing the content of fallback raw-content elements (`<iframe>`, `<noembed>`, `<noframes>`, and `<noscript>`).

When rendering dynamic text content inside fallback raw-content elements via template bindings, the template engine expects the browser to render the content safely. Under Server-Side Rendering (SSR), `domino` is configured with scripting enabled, meaning these elements are treated as raw-text elements.

However, `domino`'s serializer previously did not escape text nodes within fallback raw-content elements (`<iframe>`, `<noembed>`, `<noframes>`, `<noscript>`) during DOM serialization. As a result, any occurrence of closing tags in the bound dynamic text was not escaped.

The unescaped closing tag could be serialized directly into the output HTML. When parsed by a browser or re-parsed during SSR post-processing without preserving raw-content parser state, an injected closing tag closes the element early, allowing an injected script block to execute in the user's browser context, causing same-origin Cross-Site Scripting (XSS).

Impact

This vulnerability allows an attacker to perform same-origin Cross-Site Scripting (XSS) attacks against any user visiting an SSR-rendered page that binds user-controlled data inside fallback raw-content elements (`<iframe>`, `<noembed>`, `<noframes>`, `<noscript>`). This can lead to session hijacking, credentials theft, unauthorized actions on behalf of users, and defacement.

Patched Versions
  • 22.0.7
  • 21.2.19
  • 20.3.27

### Workarounds
If you cannot immediately update your dependencies, you can mitigate this issue using any of the following approaches:
- Disable critical CSS inlining: Critical CSS inlining in Angular SSR post-processes the rendered HTML using `domino`. Disabling this step prevents `domino` from re-parsing and re-serializing the HTML during server-side rendering.
- In `angular.json`, set `inlineCritical` to `false` under style optimization options:
```json
{
"projects": {
"my-app": {
"architect": {
"build": {
"builder": "@angular/build:application",
"options": {
"optimization": {
"styles": {
"inlineCritical": false
}
}
}
}
}
}
}
}
```
- When rendering programmatically with `CommonEngine`, set `inlineCriticalCss: false` in your render options.
- Avoid binding user-controlled values inside fallback raw-content elements (`<iframe>`, `<noembed>`, `<noframes>`, `<noscript>`).
- Sanitize user input placed inside these elements to explicitly strip or escape closing tags before passing it to the template.

Versiones

Rangos afectados

Afectada Corregida Última
@angular/platform-server≤ 19.2.25
@angular/platform-server≥ 20.0.0-next.0 < 20.3.27
@angular/platform-server≥ 21.0.0-next.0 < 21.2.19
@angular/platform-server≥ 22.0.0-next.0 < 22.0.7
19.2.25
20.0.0-next.0
20.3.27
21.0.0-next.0
21.2.19
22.0.0-next.0
22.0.7
22.2.6
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npm@angular/platform-server
Corregida 20.3.27, 21.2.19, 22.0.7 -5 d · -5 d · -18 d 22.2.6 no afectada
Versiones corregidas20.3.2721.2.1922.0.7
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://github.com/angular/angular/security/advisories/GHSA-vpx6-8pjr-4g3v
Otrahttps://github.com/angular/angular/pull/69675
Otrahttps://github.com/angular/angular/pull/69714
Otrahttps://github.com/angular/angular/pull/69929
Otrahttps://github.com/angular/angular/pull/69930
Otrahttps://github.com/angular/domino/pull/32
Otrahttps://github.com/angular/domino/commit/f88e5aa49cf2804d7c2df22ef1640eb4ec43dd56
Otrahttps://github.com/angular/angular

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.