CVE-2026-65117

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.2% (9th percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause use of a hard-coded password. A successful exploit of this vulnerability might lead to data tampering, denial of service, and information disclosure.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 22, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Sep 22, 2026
No patch confirmed yet.
generic
https://www.cve.org/CVERecord?id=CVE-2026-65117

Vendor Advisories for CVE-2026-65117(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 24× in last 7d / 39× 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-10-04 04:44 UTCGHSA enrichment
  2. 2026-10-03 15:35 UTCEG score recompute
  3. 2026-10-03 15:35 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 02:25 UTCEG score recompute
  6. 2026-10-03 02:25 UTCGHSA enrichment
  7. 2026-10-02 17:56 UTCEPSS rescore
  8. 2026-10-02 13:15 UTCGHSA enrichment
  9. 2026-10-02 00:05 UTCEG score recompute
  10. 2026-10-02 00:05 UTCGHSA enrichment
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-10-01 10:05 UTCGHSA enrichment
  13. 2026-09-30 20:57 UTCEG score recompute
  14. 2026-09-30 20:57 UTCGHSA enrichment
  15. 2026-09-30 15:03 UTCEPSS rescore
  16. 2026-09-30 07:48 UTCGHSA enrichment
  17. 2026-09-29 18:39 UTCEG score recompute▲ 3.80
  18. 2026-09-29 18:39 UTCGHSA enrichment
  19. 2026-09-29 18:38 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  20. 2026-09-29 00:20 UTCEG score recompute
  21. 2026-09-29 00:20 UTCGHSA enrichment
  22. 2026-09-28 13:51 UTCEPSS rescore
  23. 2026-09-27 23:37 UTCEG score recompute
  24. 2026-09-27 23:37 UTCGHSA enrichment
  25. 2026-09-26 22:56 UTCEG score recompute
Show 14 more
  1. 2026-09-26 22:56 UTCGHSA enrichment
  2. 2026-09-26 15:59 UTCEPSS rescore
  3. 2026-09-25 22:14 UTCGHSA enrichment
  4. 2026-09-24 21:28 UTCEG score recompute
  5. 2026-09-24 21:28 UTCGHSA enrichment
  6. 2026-09-23 20:32 UTCEG score recompute
  7. 2026-09-23 20:32 UTCGHSA enrichment
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-22 19:51 UTCGHSA enrichment
  10. 2026-09-22 16:20 UTCEG score recompute
  11. 2026-09-22 16:20 UTCGHSA enrichment
  12. 2026-09-22 15:19 UTCEG score recompute
  13. 2026-09-22 14:28 UTCEG score recompute
  14. 2026-09-22 14:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-65117?
CVE-2026-65117 is a high vulnerability published on September 22, 2026. NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause use of a hard-coded password. A successful exploit of this vulnerability might lead to data tampering, denial of service, and information disclosure.
When was CVE-2026-65117 disclosed?
CVE-2026-65117 was first published on September 22, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65117 actively exploited?
CVE-2026-65117 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65117?
CVE-2026-65117 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-65117?
No fix for CVE-2026-65117 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-65117 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-65117?

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

Book a Demo →Browse All CVEs