CVE-2026-86836

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In Eclipse Ankaios versions 0.1.0 through 1.0.2, the agent creates workload files and Control Interface named pipes (FIFOs) under a predictable path derived from the agent name and a hash of the workload's runtime configuration. If a directory or FIFO already exists at that path when the agent (re)starts, the agent reuses it based only on an existence and/or file-type check, without validating its owner or permissions. A local, unprivileged user with write access to the same base directory (by default under $TMPDIR/ankaios, e.g. shared /tmp) can pre-create this path hierarchy, including the two Control Interface FIFOs, before the agent starts. The agent then treats the attacker-owned FIFOs as the legitimate Control Interface for the targeted workload. The attacker can complete the Control Interface handshake and issue requests using that workload's configured controlInterfaceAccess permissions, allowing impersonation of the workload and, depending on its configured permissions, unauthorized reading and/or modification of the cluster's desired state.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Sep 14, 2026
No patch confirmed yet.
generic

Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/280

Vendor Advisories for CVE-2026-86836(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 20:44 UTCEG score recompute
  2. 2026-09-18 20:44 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 08:29 UTCGHSA enrichment
  5. 2026-09-17 20:43 UTCEG score recompute
  6. 2026-09-17 20:43 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 08:55 UTCGHSA enrichment
  9. 2026-09-16 21:08 UTCEG score recompute
  10. 2026-09-16 21:08 UTCGHSA enrichment
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 09:01 UTCEG score recompute
  13. 2026-09-16 09:01 UTCGHSA enrichment
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 21:14 UTCGHSA enrichment
  16. 2026-09-15 09:27 UTCEG score recompute
  17. 2026-09-15 09:27 UTCGHSA enrichment
  18. 2026-09-15 08:33 UTCEG score recompute
  19. 2026-09-15 08:33 UTCGHSA enrichment
  20. 2026-09-15 07:06 UTCGHSA enrichment
  21. 2026-09-14 19:19 UTCEG score recompute
  22. 2026-09-14 19:19 UTCGHSA enrichment
  23. 2026-09-14 18:26 UTCEG score recompute
  24. 2026-09-14 17:50 UTCEG score recompute
  25. 2026-09-14 17:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86836?
CVE-2026-86836 is a high vulnerability published on September 14, 2026. In Eclipse Ankaios versions 0.1.0 through 1.0.2, the agent creates workload files and Control Interface named pipes (FIFOs) under a predictable path derived from the agent name and a hash of the workload's runtime configuration. If a directory or FIFO already exists at that path when the agent…
When was CVE-2026-86836 disclosed?
CVE-2026-86836 was first published in the National Vulnerability Database on September 14, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86836 actively exploited?
CVE-2026-86836 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.6% of all scored CVEs.
What is the CVSS score of CVE-2026-86836?
CVE-2026-86836 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-86836?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86836, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-86836

Explore →

Is Your Infrastructure Affected by CVE-2026-86836?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.