CVE-2026-9765

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

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

Note: The CVE and blog post don't exist because we determined this is actually a cloud-only issue.

Access Controls are “Broken” when a user can access resources they are not authorized to access. An attacker can bypass any access control mechanisms in a web application, and gain unauthorized access to resources that are not available with their permissions.

Broken access control can allow attackers to: Access resources only accessible to certain users, thus allowing unauthorized access to data Perform operations on behalf of other users, leading to account takeovers in the worst cases Attempt privilege escalation Attempt to take over an account

CVSS v3
7.1
EG Score
7.1(high)
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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

July 24, 2026

Last Modified

July 30, 2026

References (1)

Vendor Advisories for CVE-2026-9765(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 28× 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-31 18:51 UTCGHSA enrichment
  2. 2026-07-31 07:18 UTCGHSA enrichment
  3. 2026-07-30 19:45 UTCEG score recompute
  4. 2026-07-30 19:45 UTCGHSA enrichment
  5. 2026-07-30 16:28 UTCEPSS rescore
  6. 2026-07-30 12:40 UTCEG score recompute
  7. 2026-07-30 12:40 UTCGHSA enrichment
  8. 2026-07-30 01:30 UTCEPSS rescore
  9. 2026-07-30 01:05 UTCGHSA enrichment
  10. 2026-07-29 13:21 UTCGHSA enrichment
  11. 2026-07-29 01:46 UTCEG score recompute
  12. 2026-07-29 01:46 UTCGHSA enrichment
  13. 2026-07-28 15:37 UTCEPSS rescore
  14. 2026-07-28 14:12 UTCGHSA enrichment
  15. 2026-07-28 02:37 UTCGHSA enrichment
  16. 2026-07-27 15:04 UTCEG score recompute
  17. 2026-07-27 15:04 UTCGHSA enrichment
  18. 2026-07-27 14:14 UTCEPSS rescore
  19. 2026-07-27 02:09 UTCEG score recompute
  20. 2026-07-27 02:09 UTCGHSA enrichment
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 14:35 UTCEG score recompute
  23. 2026-07-26 14:35 UTCGHSA enrichment
  24. 2026-07-26 03:02 UTCEG score recompute
  25. 2026-07-26 03:02 UTCGHSA enrichment
Show 3 more
  1. 2026-07-25 14:18 UTCEPSS rescore
  2. 2026-07-24 12:42 UTCEG score recompute
  3. 2026-07-24 12:41 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9765?
CVE-2026-9765 is a high vulnerability published on July 24, 2026. Note: The CVE and blog post don't exist because we determined this is actually a cloud-only issue. Access Controls are “Broken” when a user can access resources they are not authorized to access. An attacker can bypass any access control mechanisms in a web application, and gain unauthorized access…
When was CVE-2026-9765 disclosed?
CVE-2026-9765 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9765 actively exploited?
CVE-2026-9765 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 79.1% of all scored CVEs.
What is the CVSS score of CVE-2026-9765?
CVE-2026-9765 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-9765?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9765, 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

Explore the affected products and dependency analysis for CVE-2026-9765

Explore →

Is Your Infrastructure Affected by CVE-2026-9765?

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

Start Free Scan →Browse All CVEs