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.
CVE-2026-69151
This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(medium)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
August 3, 2026
Last Modified
August 11, 2026
Advisory Details (5)
Auto-updated Aug 3, 2026Cross-Site Scripting (XSS) via event-handler attributes in Angular i18n · Advisory · angular/angular · GitHub
https://github.com/angular/angular/security/advisories/GHSA-jj27-h5hq-8x99fix(compiler): restrict possible event handler check to property names longer than 2 characters
Patch available: angular/angular v22.1.0-next.1 (PR #69306 merged 2026-06-15)
https://github.com/angular/angular/pull/69306fix(compiler): disallow i18n event attributes
Patch available: angular/angular v22.1.0-next.0 (PR #68821 merged 2026-06-10)
https://github.com/angular/angular/pull/68821commit 6c41f5ca01c0 (angular/angular)
Patch available: angular/angular v22.1.0-next.0 (contains commit 6c41f5ca01c0)
https://github.com/angular/angular/commit/6c41f5ca01c0ae045fc7d929b72853a11eb55865commit 417a4071a776 (angular/angular)
Patch available: angular/angular v22.1.0-next.1 (contains commit 417a4071a776)
https://github.com/angular/angular/commit/417a4071a776464d549509ed3aec121dbd2fda5eVendor Advisories for CVE-2026-69151(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(6 across 5 ecosystems)
npm(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @angular/compiler | — | 20.3.27 | — |
| @angular/core | — | 20.3.27 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| angular.js | 1.8.2-2, 1.8.3-1, 1.8.3-2, 1.8.3-3 | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| angular.js | 1.8.3-1, 1.8.3-1+deb12u1, 1.8.3-1+deb12u1~deb11u1, 1.8.3-2, 1.8.3-3 | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| angular.js | 1.8.3-3 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| angular.js | 1.8.3-3 | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 40× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 23:16 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 01:26 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 03:36 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 05:46 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:43 UTCEG score recompute
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 09:55 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 12:06 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 16:29 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 18:40 UTCEG score recompute▼ 1.50
- 2026-08-11 18:36 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
- 2026-08-11 08:28 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 20:51 UTCEG score recompute
- 2026-08-09 13:47 UTCEPSS rescore
Show 15 moreShow fewer
- 2026-08-08 21:07 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 21:22 UTCEG score recompute
- 2026-08-06 21:37 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 21:52 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 22:08 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-03 22:21 UTCEG score recompute
- 2026-08-03 21:38 UTCEG score recompute
- 2026-08-03 17:38 UTCEG score recompute▲ 7.60
- 2026-08-03 17:36 UTCNVD updateCVSS v3 → 7.6 · CVSS v4 → 7.6
- 2026-08-03 17:09 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-69151?
When was CVE-2026-69151 disclosed?
Is CVE-2026-69151 actively exploited?
What is the CVSS score of CVE-2026-69151?
How do I remediate CVE-2026-69151?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69151
Is Your Infrastructure Affected by CVE-2026-69151?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.