How severe is CVE-2017-0359?

CVE-2017-0359 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-0359?

CVE-2017-0359 affects the following packages: diffoscope (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2017-0359?

Update diffoscope to 76 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-0359 is resolved across your whole dependency graph.

How do I detect CVE-2017-0359 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for diffoscope. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2017-0359 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2017-0359?

O3 pinpoints whether CVE-2017-0359 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2017-0359 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2017-0359, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

When was CVE-2017-0359 published, and has it been updated?

CVE-2017-0359 was published on April 13, 2018 and was last updated on March 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2017-0359

CRITICAL

CVE-2017-0359 is a critical-severity (CVSS 9.8) vulnerability in diffoscope. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2017-0359 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Diffoscope may write to arbitrary locations due to an untrusted archive

Also known asGHSA-8p5c-f328-9fvvPYSEC-2018-83

Published

Apr 13, 2018

Updated

Mar 14, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Mar 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍diffoscope

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

diffoscope before 77 writes to arbitrary locations on disk based on the contents of an untrusted archive.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`diffoscope`	all versions	76

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

diffoscope before 77 writes to arbitrary locations on disk based on the …

bugs.debian.orgNVDDec 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for diffoscope. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update diffoscope to 76 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-0359 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2017-0359 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2017-0359. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

diffoscope before 77 writes to arbitrary locations on disk based on the contents of an untrusted archive.

O3 Security · Impact-Aware SCA

Is CVE-2017-0359 in your dependencies?

O3 detects CVE-2017-0359 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works