CVE-2026-69151 Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes
Attackers can inject JavaScript via malicious translation files in Angular i18n pipelines, leading to cross-site scripting and potential code execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-69151?
CVE-2026-69151 is a high-severity cross-site scripting vulnerability in @angular angular, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.27, 21.2.19, and 22.0.1, the Angular compiler i18n pipeline permits i18n-onerror and other i18n-on event-handler attributes, allowing a lower-trust translation file to replace a static handler with executable JavaScript. This issue is fixed in versions 20.3.27, 21.2.19, and 22.0.1.
Weakness: CWE-79
Which versions are affected by CVE-2026-69151?
16 open source packages ship an affected version, including @angular/compiler and @angular/core. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@angular/compiler npm | All versions to 19.2.25 | None |
@angular/compiler npm | All versions to 19.2.25 | None |
@angular/compiler npm | From 20.0.0-next.0 | 20.3.27 |
@angular/compiler npm | From 20.0.0-next.0 | 20.3.27 |
@angular/compiler npm | From 21.0.0-next.0 | 21.2.19 |
@angular/compiler npm | From 21.0.0-next.0 | 21.2.19 |
10 more packages
@angular/compiler npm | From 22.0.0-next.0 | 22.0.1 |
@angular/compiler npm | From 22.0.0-next.0 | 22.0.1 |
@angular/core npm | All versions to 19.2.25 | None |
@angular/core npm | All versions to 19.2.25 | None |
@angular/core npm | From 20.0.0-next.0 | 20.3.27 |
@angular/core npm | From 20.0.0-next.0 | 20.3.27 |
@angular/core npm | From 21.0.0-next.0 | 21.2.19 |
@angular/core npm | From 21.0.0-next.0 | 21.2.19 |
@angular/core npm | From 22.0.0-next.0 | 22.0.1 |
@angular/core npm | From 22.0.0-next.0 | 22.0.1 |
Products include Angular Angular.
How do I fix CVE-2026-69151?
Upgrade @angular/compiler to a fixed version for your release line: 20.3.27, 21.2.19 or 22.0.1.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-69151 being exploited?
There is no known exploitation of CVE-2026-69151 in the wild and no public exploit code.
Other vulnerabilities in @angular angular
- CVE-2026-68945 Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
- CVE-2026-46417 Angular: SSRF via Hostname Hijacking in @angular/platform-server
- CVE-2026-50168 Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass
- CVE-2026-54266 Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning
- CVE-2026-41423 Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
Sources
Also known as CLSA-2026-1786739230, CLSA-2026-1786741144, CLSA-2026-1786742832, CLSA-2026-1786743905, CLSA-2026-1786747673, CLSA-2026-1786793413 and 26 more.