llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · @angular/core

GHSA-PRJF-86W9-MFQV

Angular i18n vulnerable to Cross-Site Scripting

Parche disponible
Descargar PNG JSON
CVSS
—
high
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche4 versionesPrimer parche a -2 d de la divulgación
Exposición265 dDesde la divulgación, 27 feb 2026, 1:33 p. m.
Detección262 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche 19.2.19 +3
Monitoreo
Detectada
25 feb 26
27 feb 26
10 sept 26
17 nov 26
20 nov 26
25 feb 26
3 may 26
9 jul 26
14 sept 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 19.2.19 @angular/core · -2 d desde divulgación
Remediación Parche 20.3.17 @angular/core · -2 d desde divulgación
Remediación Parche 21.1.6 @angular/core · -2 d desde divulgación
Remediación Parche 21.2.0 @angular/core · -2 d desde divulgación
Divulgación Publicada GHSA-PRJF-86W9-MFQV 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) https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/XSS vulnerability has been identified in the Angular internationalization (i18n) pipeline. In ICU messages (International Components for Unicode), HTML from translated content was not properly sanitized and could execute arbitrary JavaScript.

Angular i18n typically involves three steps, extracting all messages from an application in the source language, sending the messages to be translated, and then merging their translations back into the final source code. Translations are frequently handled by contracts with specific partner companies, and involve sending the source messages to a separate contractor before receiving final translations for display to the end user.

If the returned translations have malicious content, it could be rendered into the application and execute arbitrary JavaScript.

### Impact
When successfully exploited, this vulnerability allows for execution of attacker controlled JavaScript in the application origin. Depending on the nature of the application being exploited this could lead to:

  • Credential Exfiltration: Stealing sensitive user data stored in page memory, LocalStorage, IndexedDB, or cookies available to JS and sending them to an attacker controlled server.
  • Page Vandalism: Mutating the page to read or act differently than intended by the developer.
Attach Preconditions
  • The attacker must compromise the translation file (xliff, xtb, etc.).
  • Unlike most XSS vulnerabilities, this one is not exploitable by arbitrary users. An attacker must first compromise an application's translation file before they can escalate privileges into the Angular application client.
  • The victim application must use Angular i18n.
  • The victim application must use one or more ICU messages.
  • The victim application must render an ICU message.
  • The victim application must not defend against XSS via a safe Content-Security Policy (CSP) https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP or Trusted Types https://developer.mozilla.org/en-US/docs/Web/API/Trusted_Types_API.

### Patches
- 21.2.0
- 21.1.6
- 20.3.17
- 19.2.19

### Workarounds
Until the patch is applied, developers should consider:

  • Reviewing and verifying translated content received from untrusted third parties before incorporating it in an Angular application.
  • Enabling strict CSP controls to block unauthorized JavaScript from executing on the page.
  • Enabling Trusted Types https://angular.dev/best-practices/security#enforcing-trusted-types to enforce proper HTML sanitization.
References
  • Fix https://github.com/angular/angular/pull/67183

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida Última
@angular/core≤ 18.2.14
@angular/core≥ 19.0.0-next.0 < 19.2.19
@angular/core≥ 20.0.0-next.0 < 20.3.17
@angular/core≥ 21.0.0-next.0 < 21.1.6
@angular/core≥ 21.2.0-next.0 < 21.2.0
18.2.14
19.0.0-next.0
19.2.19
20.0.0-next.0
20.3.17
21.0.0-next.0
21.1.6
21.2.0-next.0
21.2.0
22.2.6
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npm@angular/core
Corregida 19.2.19, 20.3.17, 21.1.6, 21.2.0 -2 d · -2 d · -2 d · -2 d 22.2.6 no afectada
Versiones corregidas19.2.1920.3.1721.1.621.2.0
Explotación

Arsenal público

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

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-27970
Otrahttps://github.com/angular/angular/security/advisories/GHSA-prjf-86w9-mfqv
Otrahttps://github.com/angular/angular/pull/67183
Otrahttps://github.com/angular/angular/commit/306f367899dfc2e04238fecd3455547b5d54075d
Otrahttps://github.com/angular/angular/commit/7d58b798c626bb0e4e5f89ca8affdce4f352b232
Otrahttps://github.com/angular/angular/commit/b85830953281ff3a1a77bbfe69019d352d509c93
Otrahttps://angular.dev/best-practices/security#enforcing-trusted-types
Otrahttps://developer.mozilla.org/en-US/docs/Web/API/Trusted_Types_API
Otrahttps://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP
Otrahttps://developer.mozilla.org/en-US/docs/Web/Security/Attacks/XSS
Otrahttps://github.com/angular/angular

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