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.3%, top 73% 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.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 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)
EG Risk
32(Track)
EG Risk 32/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 computed
Severity61% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

June 15, 2026

Last Modified

July 9, 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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.2-2, 1.8.3-1, 1.8.3-2, 1.8.3-3——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
angular.js1.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)
PackageVulnerable rangeFixed inDependents
angular.js1.8.3-3——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
angular.js1.8.3-3——
npm(1)
PackageVulnerable rangeFixed inDependents
@angular/compiler—20.3.25—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 104 total refreshes for this CVE.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 23:34 UTCEG score recompute
  4. 2026-08-23 09:48 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 11:57 UTCEG score recompute
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 12:30 UTCEG score recompute
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-19 13:14 UTCEG score recompute
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 08:24 UTCEG score recompute
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 09:22 UTCEG score recompute
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 10:21 UTCEG score recompute
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 10:59 UTCEG score recompute
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 11:58 UTCEG score recompute
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-11 13:50 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 75 more
  1. 2026-08-09 15:47 UTCEG score recompute
  2. 2026-08-09 13:46 UTCEPSS rescore
  3. 2026-08-08 16:46 UTCEG score recompute
  4. 2026-08-08 16:37 UTCEPSS rescore
  5. 2026-08-07 17:44 UTCEG score recompute
  6. 2026-08-06 18:43 UTCEG score recompute
  7. 2026-08-06 13:47 UTCEPSS rescore
  8. 2026-08-05 19:42 UTCEG score recompute
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-04 15:42 UTCEG score recompute
  11. 2026-08-04 15:10 UTCEPSS rescore
  12. 2026-08-04 10:39 UTCEPSS rescore
  13. 2026-08-03 10:36 UTCEPSS rescore
  14. 2026-08-02 07:52 UTCEG score recompute
  15. 2026-08-02 02:27 UTCEPSS rescore
  16. 2026-08-01 08:51 UTCEG score recompute
  17. 2026-08-01 04:16 UTCEPSS rescore
  18. 2026-07-31 04:31 UTCEG score recompute
  19. 2026-07-30 16:28 UTCEPSS rescore
  20. 2026-07-30 05:12 UTCEG score recompute
  21. 2026-07-30 01:30 UTCEPSS rescore
  22. 2026-07-29 03:27 UTCEG score recompute
  23. 2026-07-28 15:37 UTCEPSS rescore
  24. 2026-07-28 01:54 UTCEG score recompute
  25. 2026-07-26 20:13 UTCEG score recompute
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-24 14:18 UTCEPSS rescore
  29. 2026-07-23 14:18 UTCEPSS rescore
  30. 2026-07-23 03:19 UTCEG score recompute
  31. 2026-07-22 14:08 UTCEPSS rescore
  32. 2026-07-21 15:25 UTCEPSS rescore
  33. 2026-07-20 17:08 UTCEPSS rescore
  34. 2026-07-19 14:31 UTCEPSS rescore
  35. 2026-07-19 14:31 UTCEPSS rescore
  36. 2026-07-19 02:29 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-16 17:03 UTCEPSS rescore
  39. 2026-07-15 16:57 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 02:00 UTCEPSS rescore
  42. 2026-07-15 02:00 UTCEPSS rescore
  43. 2026-07-13 22:31 UTCEPSS rescore
  44. 2026-07-13 06:13 UTCEPSS rescore
  45. 2026-07-13 06:13 UTCEPSS rescore
  46. 2026-07-12 05:46 UTCEPSS rescore
  47. 2026-07-11 08:27 UTCEPSS rescore
  48. 2026-07-11 08:27 UTCEPSS rescore
  49. 2026-07-09 19:10 UTCEPSS rescore
  50. 2026-07-09 19:10 UTCEPSS rescore
  51. 2026-07-08 15:16 UTCEPSS rescore
  52. 2026-07-08 15:16 UTCEPSS rescore
  53. 2026-07-07 13:46 UTCEPSS rescore
  54. 2026-07-07 13:46 UTCEPSS rescore
  55. 2026-07-06 16:27 UTCEPSS rescore
  56. 2026-07-06 16:27 UTCEPSS rescore
  57. 2026-07-06 02:23 UTCEPSS rescore
  58. 2026-07-06 02:23 UTCEPSS rescore
  59. 2026-07-05 02:31 UTCEPSS rescore
  60. 2026-07-05 02:30 UTCEPSS rescore
  61. 2026-07-04 06:31 UTCEPSS rescore
  62. 2026-07-04 06:31 UTCEPSS rescore
  63. 2026-07-01 15:07 UTCEPSS rescore
  64. 2026-06-30 23:22 UTCEPSS rescore
  65. 2026-06-29 14:06 UTCEPSS rescore
  66. 2026-06-29 14:06 UTCEPSS rescore
  67. 2026-06-28 14:07 UTCEPSS rescore
  68. 2026-06-28 04:56 UTCEPSS rescore
  69. 2026-06-28 04:56 UTCEPSS rescore
  70. 2026-06-27 13:18 UTCEG score recompute▲ 0.80
  71. 2026-06-27 03:08 UTCEPSS rescore
  72. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 6.1
  73. 2026-06-25 13:49 UTCEPSS rescore
  74. 2026-06-24 14:05 UTCEPSS rescore
  75. 2026-06-23 21:33 UTCEPSS rescore

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 July 9, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 73.0% of all scored CVEs.
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