Advisory

GHSA-jj27-h5hq-8x99

Also known as: CVE-2026-69151

Summary

Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes

Details

A Cross-Site Scripting (XSS) vulnerability has been identified in the Angular compiler's internationalization (i18n) pipeline. Although Angular disallows binding to event-handler attributes such as onclick and onerror through standard attribute validation (validateAttribute() / validateProperty()), the i18n metadata collection path allowed these same attribute names to be marked for translation using i18n-on* attributes (e.g., i18n-onerror).

When exploited, a lower-trust translation file could replace a benign static handler such as onerror="void 0" with arbitrary executable JavaScript in the localized build.

The following example illustrates a vulnerable pattern:

<img src="foo.jpg" onerror="void 0" i18n-onerror />

Impact

When exploited, this vulnerability allows arbitrary JavaScript execution within the context of the vulnerable application's domain if an attacker can control or influence the translation files used during localization. This can lead to:

  • Session Hijacking: Accessing session cookies, tokens, or sensitive user data.
  • Unauthorized Actions: Performing actions on behalf of the authenticated user.

Patched Versions

  • 22.0.1
  • 21.2.19
  • 20.3.27

Workarounds

Ensure that static event-handler attributes (e.g., onerror, onclick) are never marked for internationalization (i18n-on*) in application templates, and ensure translation files are sourced from trusted origins.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-08-03 16:23 UTC
Modified
2026-08-03 16:41 UTC

Affected packages and fixes

@angular/compiler

npm · All systems

Affected

  • introduced 22.0.0-next.0, fixed 22.0.1 (semver)

Fixed versions

22.0.1

Fix

@angular/compiler

npm · All systems

Affected

  • introduced 21.0.0-next.0, fixed 21.2.19 (semver)

Fixed versions

21.2.19

Fix

@angular/compiler

npm · All systems

Affected

  • introduced 20.0.0-next.0, fixed 20.3.27 (semver)

Fixed versions

20.3.27

Fix

@angular/compiler

npm · All systems

Affected

  • introduced 0, last affected 19.2.25 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

@angular/core

npm · All systems

Affected

  • introduced 22.0.0-next.0, fixed 22.0.1 (semver)

Fixed versions

22.0.1

Fix

@angular/core

npm · All systems

Affected

  • introduced 21.0.0-next.0, fixed 21.2.19 (semver)

Fixed versions

21.2.19

Fix

@angular/core

npm · All systems

Affected

  • introduced 20.0.0-next.0, fixed 20.3.27 (semver)

Fixed versions

20.3.27

Fix

@angular/core

npm · All systems

Affected

  • introduced 0, last affected 19.2.25 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences