# CVE-2026-86002: Dokku: Host Command Execution via eval of Unsanitized Docker Options in DOCKER_ARGS


- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-fccf-j7qf-2xp9

## What is CVE-2026-86002?

CVE-2026-86002 is a critical vulnerability in dokku, published on 14 Oct 2026. 

### Official description

Dokku is a docker-powered platform as a service. In Dokku versions before 0.38.25, a user with app-level Dokku access and remote SSH access to execute docker-options commands can store arbitrary strings through the docker-options plugin, and those strings are later concatenated into DOCKER_ARGS and processed by Bash eval during build, deploy, or run operations. Shell command substitutions in the stored values are interpreted on the host, allowing arbitrary command execution with the privileges of the dokku operating-system user. This issue is fixed in version 0.38.25.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2026-86002?


## How do I fix CVE-2026-86002?

No fix has been published for CVE-2026-86002 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86002 being exploited?

There is no known exploitation of CVE-2026-86002 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86002 and fix it if it is affected.

What it is: CVE-2026-86002 is a critical vulnerability in dokku, published on 14 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-86002 in the wild and no public exploit code.

Affected product: dokku. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-86002/ (Markdown: https://insights.sbomify.com/CVE-2026-86002/index.md)
```

## Sources

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

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