CVE-2026-31988

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-03-12. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-11482 (ENISA EUVD) · GHSA-gmq8-994r-jv83 (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

yauzl (aka Yet Another Unzip Library) version 3.2.0 for Node.js contains an off-by-one error in the NTFS extended timestamp extra field parser within the getLastModDate() function. The while loop condition checks cursor < data.length + 4 instead of cursor + 4 <= data.length, allowing readUInt16LE() to read past the buffer boundary. A remote attacker can cause a denial of service (process crash via ERR_OUT_OF_RANGE exception) by sending a crafted zip file with a malformed NTFS extra field. This affects any Node.js application that processes zip file uploads and calls entry.getLastModDate() on parsed entries. Fixed in version 3.2.1.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

March 11, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github_commit.
Web page

Denial of Service in yauzl 3.2.0: One Zip File Crashes the Library Behind VS Code and Electron

https://www.codeant.ai/security-research/yauzl-denial-of-service-zip-file-crash
Web pageMentions a patch (unverified)

yauzl 3.2.0 - Denial of Service via Off-by-One Error in NTFS Timestamp Parser | Advisories | VulnCheck

https://www.vulncheck.com/advisories/yauzl-denial-of-service-via-off-by-one-error-in-ntfs-timestamp-parser
GitHub commit

commit c4695215b05c (thejoshwolfe/yauzl)

Fix landed in thejoshwolfe/yauzl commit c4695215b05c — awaiting tagged release

https://github.com/thejoshwolfe/yauzl/commit/c4695215b05c6adffda613b9051a2a85429b33fe

Vendor Advisories for CVE-2026-31988(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17809307402026-06-09redhat
npmyauzl @ 3.2.1 (fixes = 3.2.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
yauzl3.2.0
  • 3.2.0 up to 3.2.1: fixed in 3.2.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 95 of 241 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-01 07:54 UTCGHSA enrichmentGHSA-gmq8-994r-jv83 · GitHub severity MODERATE · GitHub CVSS 5.3
  5. 2026-11-01 07:54 UTCEG score recompute
  6. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-30 22:25 UTCOSV refresh
  8. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-10-25 14:36 UTCEG score recompute
  15. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-23 03:48 UTCEG score recompute
  18. 2026-10-23 03:48 UTCVendor advisory
  19. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-10-18 03:48 UTCEG score recompute
  25. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 70 more
  1. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  5. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-10-12 16:14 UTCEG score recompute
  7. 2026-10-11 19:57 UTCEG score recompute
  8. 2026-10-11 17:10 UTCEG score recompute
  9. 2026-10-11 14:38 UTCEG score recompute
  10. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-11 11:47 UTCOSV refresh
  12. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  17. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  19. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  20. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  24. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-09-21 23:46 UTCOSV refresh
  26. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  28. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  37. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  38. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-09-02 19:40 UTCOSV refresh
  40. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  42. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  43. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  46. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  47. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  48. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  49. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  50. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  51. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  52. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  53. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  54. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  55. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  56. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  57. 2026-08-16 11:49 UTCEG score recompute
  58. 2026-08-16 11:49 UTCVendor advisory
  59. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  60. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  61. 2026-08-14 07:46 UTCEG score recompute
  62. 2026-08-14 07:46 UTCVendor advisory
  63. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  64. 2026-08-12 22:52 UTCEG score recompute
  65. 2026-08-12 22:52 UTCVendor advisory
  66. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  67. 2026-08-11 07:08 UTCEG score recompute
  68. 2026-08-11 07:08 UTCVendor advisory
  69. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  70. 2026-08-10 07:17 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-31988?
CVE-2026-31988 is a medium-severity vulnerability; its CVE record was published on March 11, 2026. yauzl (aka Yet Another Unzip Library) version 3.2.0 for Node.js contains an off-by-one error in the NTFS extended timestamp extra field parser within the getLastModDate() function. The while loop condition checks cursor < data.length + 4 instead of cursor + 4 <= data.length, allowing readUInt16LE()…
When was CVE-2026-31988 made public?
CVE-2026-31988 was made public on February 28, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on March 11, 2026. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-31988 actively exploited?
CVE-2026-31988 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31988?
CVE-2026-31988 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-31988?
A fix for CVE-2026-31988 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-31988 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-31988

Explore →

Is Your Infrastructure Affected by CVE-2026-31988?

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