# CVE-2016-1000282: Critical severity vulnerability that affects Haraka

> An attacker can execute arbitrary commands on the server via the zip attachment processing plugin in Haraka mail server.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Feb 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w5m8-5v9m-xhx5

## What is CVE-2016-1000282?

CVE-2016-1000282 is a critical command injection vulnerability in n/a, published on 5 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2016-1000282?

2 open source packages ship an affected version, including Haraka. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Haraka` | npm | All versions | 2.8.9 |
| `Haraka` | npm | All versions | 2.8.9 |

Products: Haraka Project Haraka.

## How do I fix CVE-2016-1000282?

Upgrade Haraka to 2.8.9 or later.

## Is CVE-2016-1000282 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-1000282 exists.

Public exploit code:

- Haraka SMTP Command Injection (metasploit)

## Other vulnerabilities in n/a

- [CVE-2026-34752](https://insights.sbomify.com/CVE-2026-34752/): Haraka affected by DoS via `__proto__` email header (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1000282 and fix it if it is affected.

What it is: CVE-2016-1000282 is a critical command injection vulnerability in n/a, published on 5 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-1000282 exists.

Affected packages and fixed versions:
- Haraka (npm): affected all versions; fixed in 2.8.9
- Haraka (npm): affected all versions; fixed in 2.8.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-1000282/ (Markdown: https://insights.sbomify.com/CVE-2016-1000282/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-1000282
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-1000282
- OSV: https://osv.dev/vulnerability/CVE-2016-1000282

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-1000282/
Summaries are generated and may contain mistakes; the official description above is the record.