CVE-2026-65087

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (3rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.6 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-25) is not newer than that change (2026-09-01), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

NVIDIA NemoClaw contains a vulnerability where an attacker could cause insufficiently protected credentials . A successful exploit of this vulnerability might lead to information disclosure and data tampering.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

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 (value × EchelonGraph’s weight)
Severity61% × 45%
The EG Score, 6.1 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.2%
EPSS %ILE
3rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
Fix referenced — no release confirmed yet.
Web page

product-security/2026/5872 at main · NVIDIA/product-security · GitHub

https://github.com/NVIDIA/product-security/tree/main/2026/5872
Web page
https://www.cve.org/CVERecord?id=CVE-2026-65087

Vendor Advisories for CVE-2026-65087(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)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
uff0.0.1.dev4, 0.0.1.dev5
  • every version through 0.0.1: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 69× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 122 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 22 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-65087?
CVE-2026-65087 is a medium-severity vulnerability; its CVE record was published on August 25, 2026. NVIDIA NemoClaw contains a vulnerability where an attacker could cause insufficiently protected credentials . A successful exploit of this vulnerability might lead to information disclosure and data tampering.
When was the CVE record for CVE-2026-65087 published?
The CVE record for CVE-2026-65087 was published on August 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-65087 actively exploited?
CVE-2026-65087 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65087?
CVE-2026-65087 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-65087?
A fix for CVE-2026-65087 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-65087 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-65087?

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

Book a Demo →Browse All CVEs