CVE-2026-9650

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5EG
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.5Exploit: None knownExposed: 0

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

CWE-522 Insufficiently Protected Credentials vulnerability that could cause unauthorized access and exposure of sensitive information when unauthenticated attacker accesses credentials stored within firmware or system files. With this credential an attacker could subsequently compromise the device if they have physical access to the device.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 14, 2026

References (1)

Vendor Advisories for CVE-2026-9650(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 16× in last 7d / 74× 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-28 21:10 UTCEG score recompute
  2. 2026-07-28 21:10 UTCGHSA enrichment
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-28 06:11 UTCGHSA enrichment
  5. 2026-07-27 17:22 UTCEG score recompute
  6. 2026-07-27 17:22 UTCGHSA enrichment
  7. 2026-07-27 14:14 UTCEPSS rescore
  8. 2026-07-27 03:48 UTCGHSA enrichment
  9. 2026-07-26 14:59 UTCEG score recompute
  10. 2026-07-26 14:59 UTCGHSA enrichment
  11. 2026-07-26 14:54 UTCEPSS rescore
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-24 14:18 UTCEPSS rescore
  14. 2026-07-23 14:18 UTCEPSS rescore
  15. 2026-07-23 03:23 UTCEG score recompute
  16. 2026-07-22 14:08 UTCEPSS rescore
  17. 2026-07-21 15:25 UTCEPSS rescore
  18. 2026-07-21 15:25 UTCEPSS rescore
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-19 14:31 UTCEPSS rescore
  21. 2026-07-19 02:29 UTCEPSS rescore
  22. 2026-07-18 10:04 UTCEPSS rescore
  23. 2026-07-16 18:44 UTCGHSA enrichment
  24. 2026-07-16 17:03 UTCEPSS rescore
  25. 2026-07-16 05:56 UTCGHSA enrichment
Show 60 more
  1. 2026-07-15 17:08 UTCGHSA enrichment
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 04:14 UTCEG score recompute▼ 1.20
  4. 2026-07-15 04:14 UTCGHSA enrichment
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-14 16:03 UTCNVD updateCVSS v3 → 7.5
  7. 2026-07-14 15:15 UTCGHSA enrichment
  8. 2026-07-14 02:27 UTCGHSA enrichment
  9. 2026-07-13 22:31 UTCEPSS rescore
  10. 2026-07-13 13:40 UTCGHSA enrichment
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 00:51 UTCGHSA enrichment
  13. 2026-07-12 11:55 UTCGHSA enrichment
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-11 23:06 UTCGHSA enrichment
  16. 2026-07-11 10:18 UTCGHSA enrichment
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-10 21:30 UTCGHSA enrichment
  19. 2026-07-10 08:42 UTCGHSA enrichment
  20. 2026-07-09 19:53 UTCGHSA enrichment
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-09 07:05 UTCGHSA enrichment
  23. 2026-07-08 18:16 UTCGHSA enrichment
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-08 05:27 UTCGHSA enrichment
  26. 2026-07-07 16:40 UTCGHSA enrichment
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-07 03:28 UTCGHSA enrichment
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 14:40 UTCGHSA enrichment
  31. 2026-07-06 02:23 UTCEPSS rescore
  32. 2026-07-06 01:49 UTCGHSA enrichment
  33. 2026-07-05 13:01 UTCGHSA enrichment
  34. 2026-07-05 02:31 UTCEPSS rescore
  35. 2026-07-05 00:13 UTCGHSA enrichment
  36. 2026-07-04 11:22 UTCGHSA enrichment
  37. 2026-07-04 06:31 UTCEPSS rescore
  38. 2026-07-03 22:34 UTCGHSA enrichment
  39. 2026-07-03 09:43 UTCGHSA enrichment
  40. 2026-07-02 20:54 UTCGHSA enrichment
  41. 2026-07-02 08:06 UTCGHSA enrichment
  42. 2026-07-01 19:19 UTCGHSA enrichment
  43. 2026-07-01 15:07 UTCEPSS rescore
  44. 2026-07-01 06:31 UTCGHSA enrichment
  45. 2026-06-30 23:22 UTCEPSS rescore
  46. 2026-06-30 17:42 UTCGHSA enrichment
  47. 2026-06-30 04:53 UTCGHSA enrichment
  48. 2026-06-29 15:46 UTCGHSA enrichment
  49. 2026-06-29 14:06 UTCEPSS rescore
  50. 2026-06-29 02:58 UTCGHSA enrichment
  51. 2026-06-28 14:10 UTCGHSA enrichment
  52. 2026-06-28 14:07 UTCEPSS rescore
  53. 2026-06-28 04:56 UTCEPSS rescore
  54. 2026-06-28 01:22 UTCGHSA enrichment
  55. 2026-06-27 12:33 UTCGHSA enrichment
  56. 2026-06-27 03:08 UTCEPSS rescore
  57. 2026-06-26 23:45 UTCGHSA enrichment
  58. 2026-06-26 10:57 UTCGHSA enrichment
  59. 2026-06-25 17:49 UTCEG score recompute
  60. 2026-06-25 17:48 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-9650?
CVE-2026-9650 is a high vulnerability published on June 25, 2026. CWE-522 Insufficiently Protected Credentials vulnerability that could cause unauthorized access and exposure of sensitive information when unauthenticated attacker accesses credentials stored within firmware or system files. With this credential an attacker could subsequently compromise the device…
When was CVE-2026-9650 disclosed?
CVE-2026-9650 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9650 actively exploited?
CVE-2026-9650 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 84.8% of all scored CVEs.
What is the CVSS score of CVE-2026-9650?
CVE-2026-9650 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-9650?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9650, 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-9650

Explore →

Is Your Infrastructure Affected by CVE-2026-9650?

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

Start Free Scan →Browse All CVEs