CVE-2026-86002

waiting for further signalsZero needs more public information before it can validate it.

GHSA-fccf-j7qf-2xp9 ↗EUVD-2026-101291 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
dokku < 0.38.24
fixed in 0.38.25
CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
ETK-2026-1588Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 10h 09msince last run
34mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+50h42m
0
+2h
+4h
+6h
+8h
+10h

description

Dokku versions earlier than 0.38.25 mishandle Docker option values supplied through the docker-options plugin. An attacker with app-level Dokku permissions and SSH access to use those commands can cause host-side commands to run as the Dokku system user during application operations.

mitigation

Upgrade Dokku to version 0.38.25 or later. Until upgraded, restrict SSH and app-level access that permits use of docker-options commands.

fixed in 0.38.25

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.56%45th percentile
agent run time
34m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 15:55Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-14 15:55Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-86002

{
  "etk_id": "ETK-2026-1588",
  "cve_id": "CVE-2026-86002",
  "display_id": "CVE-2026-86002",
  "ghsa_id": "GHSA-fccf-j7qf-2xp9",
  "euvd_id": "EUVD-2026-101291",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Shell injection through Docker options in Dokku",
  "summary": "Dokku versions earlier than 0.38.25 mishandle Docker option values supplied through the docker-options plugin. An attacker with app-level Dokku permissions and SSH access to use those commands can cause host-side commands to run as the Dokku system user during application operations.",
  "mitigation": "Upgrade Dokku to version 0.38.25 or later. Until upgraded, restrict SSH and app-level access that permits use of docker-options commands.",
  "vendor": "dokku",
  "product": "dokku",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 0.38.24"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.38.25"
      ],
      "package_name": "dokku",
      "purl": null
    }
  ],
  "cwes": [
    95
  ],
  "cvss_score": 9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H",
  "epss_score": 0.0056,
  "epss_percentile": 0.4575,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 34.450649383333335,
  "t0_at": "2026-10-14T15:55:30.015000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T15:55:30.015000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T15:55:30.015000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-86002"
    }
  }
}

published 2026-10-14 17:08Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.