CVE-2016-1000282 — Haraka
CRITICALCVE-2016-1000282 is a critical-severity (CVSS 9.8) CWE-77 vulnerability in Haraka. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for Haraka — see the affected versions and patch details below.
Critical severity vulnerability that affects Haraka
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
HarakanpmDescription
Haraka version 2.8.8 and earlier comes with a plugin for processing attachments for zip files. Versions 2.8.8 and earlier can be vulnerable to command injection.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | Haraka | all versions | 2.8.9npm install Haraka@2.8.9 |
Affected Products
harakaharaka_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Haraka, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Haraka to 2.8.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-1000282 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2016-1000282 in your dependencies?
Find it across npm, including transitive dependencies.