Is there a public PoC exploit available for CVE-2026-69151?

Yes, a public proof-of-concept exploit is available for CVE-2026-69151. Prioritise patching immediately. EPSS: 0.3%.

How to fix or mitigate CVE-2026-69151?

Within 24 hours, inventory Angular framework versions across development environments and identify all projects using i18n features. Within 7 days, apply the vendor-released patches by upgrading to Angular versions 22.0.1, 21.2.19, or 20.3.27 depending on your current major version, and rebuild all affected applications. Within 30 days, conduct a security review of translation file management processes and restrict modification access to i18n resources to prevent future code injection.

CVE-2026-69151

Q: What is the CVSS score of CVE-2026-69151?

CVE-2026-69151 has a CVSS 4.0 base score of 7.6 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-52369 HIGH

Cross-site Scripting (XSS) (CWE-79)

2026-08-03 https://github.com/angular/angular

GHSA-jj27-h5hq-8x99

XSS

7.6

CVSS 4.0 · Vendor: https://github.com/angular/angular

Severity by source

Vendor (https://github.com/angular/angular) PRIMARY

7.6 HIGH

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

4.4 MEDIUM

Attack requires build-time control of translation files (PR:L, AC:H); XSS is delivered over the network but user must load page (UI:R); scope changes to browser context (S:C).

3.1 AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N

4.0 AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Red Hat

8.1 HIGH

qualitative

Primary rating from Vendor (https://github.com/angular/angular).

CVSS VectorVendor: https://github.com/angular/angular

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Scope

Lifecycle Timeline

Analysis Updated

Aug 03, 2026 - 17:46 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Aug 03, 2026 - 17:37 vuln.today

cvss_changed

CVSS changed

Aug 03, 2026 - 17:37 NVD

7.6 (HIGH)

Source Code Evidence Fetched

Aug 03, 2026 - 17:06 vuln.today

Analysis Generated

Aug 03, 2026 - 17:06 vuln.today

CVE Published

Aug 03, 2026 - 16:23 cve.org

HIGH

DescriptionCVE.org

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:

html

<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.

AnalysisAI

Cross-site scripting in the Angular compiler's i18n pipeline allows arbitrary JavaScript injection into localized application builds when event-handler attributes such as onerror or onclick are marked for translation using i18n-on* template directives. Angular's standard validateAttribute() and validateProperty() guards block binding to event-handler attributes at runtime, but the I18nMetaVisitor code path in packages/compiler/src/render3/view/i18n/meta.ts contained no equivalent restriction, enabling a lower-trust translation file to replace a benign handler with executable JavaScript at compile time. Patched versions 22.0.1, 21.2.19, and 20.3.27 are available; no public exploit has been identified at time of analysis.