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

GHSA-G93W-MFHG-P222

Angular vulnerable to XSS in i18n attribute bindings

Parche disponible
Descargar PNG JSON
CVSS
—
high
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche4 versionesPrimer parche a -1 d de la divulgación
Exposición251 dDesde la divulgación, 13 mar 2026, 3:56 p. m.
Detección248 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.20 +3
Monitoreo
Detectada
12 mar 26
13 mar 26
6 may 26
17 nov 26
19 nov 26
12 mar 26
14 may 26
16 jul 26
17 sept 26
19 nov 26
FechaFaseEventoDetalle
Remediación Parche 19.2.20 @angular/core · -1 d desde divulgación
Remediación Parche 20.3.18 @angular/core · -1 d desde divulgación
Remediación Parche 21.2.4 @angular/core · -1 d desde divulgación
Remediación Parche 22.0.0-next.3 @angular/core · -1 d desde divulgación
Divulgación Publicada GHSA-G93W-MFHG-P222 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 has been identified in the Angular runtime and compiler. It occurs when the application uses a security-sensitive attribute (for example href on an anchor tag) together with Angular's ability to internationalize attributes. Enabling internationalization for the sensitive attribute by adding `i18n-<attribute>` name bypasses Angular's built-in sanitization mechanism, which when combined with a data binding to untrusted user-generated data can allow an attacker to inject a malicious script.

The following example illustrates the issue:

<a href="{{maliciousUrl}}" i18n-href>Click me</a>

The following attributes have been confirmed to be vulnerable:
- `action`
- `background`
- `cite`
- `codebase`
- `data`
- `formaction`
- `href`
- `itemtype`
- `longdesc`
- `poster`
- `src`
- `xlink:href`

### Impact
When exploited, this vulnerability allows an attacker to execute arbitrary code within the context of the vulnerable application's domain. This enables:
- Session Hijacking: Stealing session cookies and authentication tokens.
- Data Exfiltration: Capturing and transmitting sensitive user data.
- Unauthorized Actions: Performing actions on behalf of the user.

### Attack Preconditions
1. The application must use a vulnerable version of Angular.
2. The application must bind unsanitized user input to one of the attributes mentioned above.
3. The bound value must be marked for internationalization via the presence of a `i18n-<name>` attribute on the same element.

### Patches
- 22.0.0-next.3
- 21.2.4
- 20.3.18
- 19.2.20

### Workarounds
The primary workaround is to ensure that any data bound to the vulnerable attributes is never sourced from untrusted user input (e.g., database, API response, URL parameters) until the patch is applied, or when it is, it shouldn't be marked for internationalization.

Alternatively, users can explicitly sanitize their attributes by passing them through Angular's `DomSanitizer`:

import {Component, inject, SecurityContext} from '@angular/core';
import {DomSanitizer} from '@angular/platform-browser';

@Component({
  template: `
    <form action="{{url}}" i18n-action>
      <button>Submit</button>
    </form>
  `,
})
export class App {
  url: string;

  constructor() {
    const dangerousUrl = 'javascript:alert(1)';
    const sanitizer = inject(DomSanitizer);
    this.url = sanitizer.sanitize(SecurityContext.URL, dangerousUrl) || '';
  }
}

### References
- Fix 1 https://github.com/angular/angular/pull/67541
- Fix 2 https://github.com/angular/angular/pull/67561

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 · @angular/compiler≥ 17.0.0-next.0 ≤ 18.2.14
@angular/core · @angular/compiler≥ 19.0.0-next.0 < 19.2.20
@angular/core · @angular/compiler≥ 20.0.0-next.0.0.0 < 20.3.18
@angular/core · @angular/compiler≥ 21.0.0-next.0 < 21.2.4
@angular/core · @angular/compiler≥ 22.0.0-next.0 < 22.0.0-next.3
17.0.0-next.0
18.2.14
19.0.0-next.0
19.2.20
20.0.0-next.0.0.0
20.3.18
21.0.0-next.0
21.2.4
22.0.0-next.0
22.0.0-next.3
22.2.6
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npm@angular/core
Corregida 19.2.20, 20.3.18, 21.2.4, 22.0.0-next.3 -1 d · -1 d · -1 d · -1 d 22.2.6 no afectada
npm@angular/compiler
Corregida 19.2.20, 20.3.18, 21.2.4, 22.0.0-next.3 -1 d · -1 d · -1 d · -1 d 22.2.6 no afectada
Versiones corregidas19.2.2020.3.1821.2.422.0.0-next.3
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-32635
Otrahttps://github.com/angular/angular/security/advisories/GHSA-g93w-mfhg-p222
Otrahttps://github.com/angular/angular/pull/67541
Otrahttps://github.com/angular/angular/pull/67561
Otrahttps://github.com/angular/angular/commit/224e60ecb1b90115baa702f1c06edc1d64d86187
Otrahttps://github.com/angular/angular/commit/78dea55351fb305b33a919c43a6b363137eca166
Otrahttps://github.com/angular/angular/commit/8630319f74c9575a21693d875cc7d5252516146d
Otrahttps://github.com/angular/angular/commit/ed2d324f9cc12aab6cfa0569ef10b73243a62c65
Otrahttps://github.com/angular/angular

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