How severe is CVE-2026-69151?

No CVSS score has been assigned to CVE-2026-69151 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-69151?

CVE-2026-69151 affects the following packages: @angular/compiler (npm), @angular/compiler (npm), @angular/compiler (npm), @angular/compiler (npm), @angular/core (npm), @angular/core (npm), @angular/core (npm), @angular/core (npm). Ecosystems affected: npm.

How do I fix CVE-2026-69151?

Update @angular/compiler to 22.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-69151 is resolved across your whole dependency graph.

How do I detect CVE-2026-69151 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @angular/compiler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-69151 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2026-69151 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-69151 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-69151?

CVE-2026-69151 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-69151?

CVE-2026-69151 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-69151 published, and has it been updated?

CVE-2026-69151 was published on August 3, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-69151 — @angular/compiler

Fix: angular/angular@417a407

CVE-2026-69151 is a Cross-site Scripting (XSS) vulnerability in @angular/compiler. A fix is available for @angular/compiler — see the affected versions and patch details below.

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

Also known asGHSA-jj27-h5hq-8x99

Published

Aug 3, 2026

Updated

Oct 28, 2026

Affected

8 pkgs

Patched

6 / 8

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-69151.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

8 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

12Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@angular/compilernpm

8.1Mdownloads / week

Description

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.

Affected Packages

8 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@angular/compiler`	≥ 22.0.0-next.0&&< 22.0.1	22.0.1`npm install @angular/compiler@22.0.1`
📦npm	`@angular/compiler`	≥ 21.0.0-next.0&&< 21.2.19	21.2.19`npm install @angular/compiler@21.2.19`
📦npm	`@angular/compiler`	≥ 20.0.0-next.0&&< 20.3.27	20.3.27`npm install @angular/compiler@20.3.27`
📦npm	`@angular/compiler`	all versions	No fix
📦npm	`@angular/core`	≥ 22.0.0-next.0&&< 22.0.1	22.0.1`npm install @angular/core@22.0.1`
📦npm	`@angular/core`	≥ 21.0.0-next.0&&< 21.2.19	21.2.19`npm install @angular/core@21.2.19`

Affected Products

1 product · 4 configurations

Application

angularangular

≥ 22.0.0 && ≤ 19.2.25

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @angular/compiler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @angular/compiler to 22.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-69151 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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 Jav

O3 Security · Impact-Aware SCA

Is CVE-2026-69151 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works