CVE-2026-85396
Path traversal in rubyzip allows writing files outside extraction directory.
Is CVE-2026-85396 being exploited?
Not confirmed. CVE-2026-85396 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-85396?
CVE-2026-85396 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-85396?
Yes. A fix has been recorded for CVE-2026-85396. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-85396 affect?
CVE-2026-85396 affects rubyzip < 3.4.0, Ruby applications that extract untrusted ZIP archives. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-85396?
Upgrade rubyzip to >= 3.4.0; avoid extracting untrusted archives and validate paths.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted ZIP entries can traverse directories to write/overwrite files outside target dir, enabling data tampering or potential code execution if placed in web or service paths.
Immediate action required
- affected< 3.4.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.