CVE-2026-54265

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 91% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, an issue in the @angular/compiler package allows bypassing DOM property sanitization through the use of two-way property bindings. Specifically, when a native DOM property that requires sanitization (such as innerHTML, srcdoc, src, href, data, or sandbox) is bound using the two-way binding syntax (e.g., [(innerHTML)]="value" or bindon-innerHTML="value"), the Angular template compiler failed to apply the appropriate schema-derived sanitizer resolution to the TwoWayProperty operation. As a result, native two-way DOM bindings were emitted without the required sanitizer function, whereas equivalent one-way bindings would be properly sanitized. This flaw enables an attacker who can control the value of a two-way bound sensitive property to bypass Angular's built-in sanitization logic, potentially leading to client-side Cross-Site Scripting (XSS). This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
9.4%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 26, 2026

Advisory Details (3)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Two-Way Property Binding Sanitization Bypass (XSS) · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-58w9-8g37-x9v5
github_pr Patch Available

fix(compiler): sanitize two-way properties

Patch available: angular/angular v22.1.0-next.0 (PR #69107 merged 2026-06-08)

https://github.com/angular/angular/pull/69107
github_commit Patch Available

commit 3c70270c9667 (angular/angular)

Patch available: angular/angular v22.1.0-next.0 (contains commit 3c70270c9667)

https://github.com/angular/angular/commit/3c70270c96677c0dd33585f2afe8e187113e5fb4

Vendor Advisories for CVE-2026-54265(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@angular/compiler———

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 38× 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.

  1. 2026-07-07 00:21 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 09:25 UTCEG score recompute
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 10:03 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 10:23 UTCEG score recompute
  13. 2026-07-02 11:18 UTCEG score recompute
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 12:02 UTCEG score recompute
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 13:01 UTCEG score recompute
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 11:20 UTCEG score recompute
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 12:18 UTCEG score recompute
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 13:18 UTCEG score recompute▲ 0.80
Show 13 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 6.1
  3. 2026-06-26 14:16 UTCEG score recompute
  4. 2026-06-25 15:10 UTCEG score recompute
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 16:08 UTCEG score recompute
  7. 2026-06-24 14:05 UTCEPSS rescore
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-23 17:07 UTCEG score recompute
  11. 2026-06-22 17:51 UTCEG score recompute▲ 5.30
  12. 2026-06-22 17:45 UTCNVD updateCVSS v3 → 5.3 · CVSS v4 → 5.3
  13. 2026-06-15 17:46 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54265?
CVE-2026-54265 is a medium vulnerability published on June 15, 2026. Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, an issue in the @angular/compiler package allows bypassing DOM property sanitization through the use of two-way property…
When was CVE-2026-54265 disclosed?
CVE-2026-54265 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54265 actively exploited?
CVE-2026-54265 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54265?
CVE-2026-54265 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-54265?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54265, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54265

Explore →

Is Your Infrastructure Affected by CVE-2026-54265?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs