CVE-2026-86095

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-05. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
7.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.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.

The CVE record's CNA (VulnCheck) lists Unidata netcdf-c versions up to and including 4.10.1 as affected. No release containing a fix is confirmed on record.

Unidata netcdf-c through 4.10.1 contains an out-of-bounds write vulnerability in NC4_HDF5_inq_attname() that copies HDF5 attribute names into a fixed 256-byte buffer without length validation. Attackers can craft HDF5 files with oversized attribute names to overflow the destination buffer, causing memory corruption and crashes when applications enumerate attribute names.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

September 4, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Sep 4, 2026
No fix on record yet.
Web page

Unidata netcdf-c through 4.10.1 Out-of-bounds Write via Oversized HDF5 Attribute Name | Advisories | VulnCheck

https://www.vulncheck.com/advisories/unidata-netcdf-c-through-4.10.1-out-of-bounds-write-via-oversized-hdf5-attribute-name
Web page

netcdf-c/libhdf5/hdf5attr.c at v4.10.1 · Unidata/netcdf-c · GitHub

https://github.com/Unidata/netcdf-c/blob/v4.10.1/libhdf5/hdf5attr.c
Web page

GitHub - Unidata/netcdf-c: Official GitHub repository for netCDF-C libraries and utilities. · GitHub

https://github.com/Unidata/netcdf-c

Vendor Advisories for CVE-2026-86095(1)

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

Affected Packages

(6 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
netcdf1:4.10.0-1 ... 1:4.9.3~rc2-1~exp1 (22 versions)
  • every version on: no fix on record
—
netcdf-parallel1:4.10.0-1 ... 1:4.9.3-2 (10 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
netcdf1:4.10.0-1, 1:4.10.0-1~exp1, 1:4.10.1-1, 1:4.9.3-1
  • every version on: no fix on record
—
netcdf-parallel1:4.10.0-1, 1:4.10.1-1, 1:4.10.1-2, 1:4.9.3-2
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
netcdf1:4.10.0-1, 1:4.10.0-1~exp1, 1:4.10.1-1, 1:4.9.3-1
  • every version on: no fix on record
—
netcdf-parallel1:4.10.0-1, 1:4.10.1-1, 1:4.10.1-2, 1:4.9.3-2
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 89× 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 149 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 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-86095?
CVE-2026-86095 is a high-severity vulnerability; its CVE record was published on September 4, 2026. Unidata netcdf-c through 4.10.1 contains an out-of-bounds write vulnerability in NC4HDF5inq_attname() that copies HDF5 attribute names into a fixed 256-byte buffer without length validation. Attackers can craft HDF5 files with oversized attribute names to overflow the destination buffer, causing…
When was the CVE record for CVE-2026-86095 published?
The CVE record for CVE-2026-86095 was published on September 4, 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-86095 actively exploited?
CVE-2026-86095 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86095?
CVE-2026-86095 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-86095?
No fix for CVE-2026-86095 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 CVE record's CNA (VulnCheck) lists Unidata netcdf-c versions up to and including 4.10.1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-86095 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-86095

Explore →

Is Your Infrastructure Affected by CVE-2026-86095?

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

Book a Demo →Browse All CVEs