CVE-2026-85396

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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.

rubyzip versions before 3.4.0 contain a path traversal vulnerability in Zip::Entry#extract that fails to properly validate extraction paths using prefix comparison without trailing separators. Attackers can craft archive entries with names like ../upload_backup/owned.sh to write files outside the intended extraction directory into sibling paths sharing the destination prefix.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 3, 2026

Advisory Details (6)

Auto-updated Sep 3, 2026
Patch available. Sources: github_commit, github_release.
generic

rubyzip before 3.4.0 Path Traversal in Zip::Entry#extract via Sibling-Directory Prefix | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rubyzip-before-3.4.0-path-traversal-in-zip-entry-extract-via-sibling-directory-prefix
generic

oss/rubyzip.md at main · geo-chen/oss · GitHub

https://github.com/geo-chen/oss/blob/main/rubyzip.md
generic

rubyzip/lib/zip/entry.rb at v3.3.1 · rubyzip/rubyzip · GitHub

https://github.com/rubyzip/rubyzip/blob/v3.3.1/lib/zip/entry.rb
github_release Patch Available

v3.4.0

Patch available: rubyzip/rubyzip v3.4.0

https://github.com/rubyzip/rubyzip/releases/tag/v3.4.0
generic

GitHub - rubyzip/rubyzip: Official Rubyzip repository · GitHub

https://github.com/rubyzip/rubyzip
github_commit Patch Available

commit 17edfbf4423b (rubyzip/rubyzip)

Patch available: rubyzip/rubyzip v3.4.0 (contains commit 17edfbf4423b)

https://github.com/rubyzip/rubyzip/commit/17edfbf4423b83211b075acc23a7d8640da63449

Vendor Advisories for CVE-2026-85396(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-zip2.3.2-1 ... 3.5.0+dfsg-1 (7 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-zip2.3.2-1 ... 3.5.0+dfsg-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-zip2.3.2-1, 3.2.2+dfsg-1, 3.2.2-1, 3.2.2-23.4.0+dfsg-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-85396?
CVE-2026-85396 is a high vulnerability published on September 3, 2026. rubyzip versions before 3.4.0 contain a path traversal vulnerability in Zip::Entry#extract that fails to properly validate extraction paths using prefix comparison without trailing separators. Attackers can craft archive entries with names like ../upload_backup/owned.sh to write files outside the…
When was CVE-2026-85396 disclosed?
CVE-2026-85396 was first published in the National Vulnerability Database on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85396 actively exploited?
CVE-2026-85396 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 67.8% of all scored CVEs.
What is the CVSS score of CVE-2026-85396?
CVE-2026-85396 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-85396?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85396, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85396?

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

Start Free Scan →Browse All CVEs