CVE-2026-18171

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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 — 3 sources updated this week
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.7Exploit: None knownExposed: 0

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

Docker Sandboxes (sbx) applies the read-only intent of a runtime host mount to the in-guest container bind only: the underlying virtio-fs host-edge grant is added to the sandbox's policy-share allowlist with no access mode. The directory stays writable at its shared-export path, so unprivileged code inside the sandbox can derive that path and write to a host directory the operator attached read-only.

CVSS v3
5.7
EG Score
5.7(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity57% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

Docker Sandboxes | Docker Docs

https://docs.docker.com/ai/sandboxes/

Vendor Advisories for CVE-2026-18171(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 27× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 15:39 UTCEG score recompute
  3. 2026-08-20 15:39 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 15:36 UTCGHSA enrichment
  6. 2026-08-18 15:33 UTCGHSA enrichment
  7. 2026-08-17 19:14 UTCEG score recompute
  8. 2026-08-17 19:14 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 18:32 UTCEG score recompute
  11. 2026-08-16 18:32 UTCGHSA enrichment
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 18:29 UTCEG score recompute
  15. 2026-08-15 18:29 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 18:25 UTCEG score recompute
  18. 2026-08-14 18:25 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 18:22 UTCGHSA enrichment
  21. 2026-08-12 18:19 UTCEG score recompute
  22. 2026-08-12 18:19 UTCGHSA enrichment
  23. 2026-08-12 17:26 UTCEG score recompute
  24. 2026-08-12 17:26 UTCGHSA enrichment
  25. 2026-08-12 15:25 UTCEG score recompute
Show 2 more
  1. 2026-08-12 15:13 UTCEG score recompute
  2. 2026-08-12 15:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18171?
CVE-2026-18171 is a medium vulnerability published on August 12, 2026. Docker Sandboxes (sbx) applies the read-only intent of a runtime host mount to the in-guest container bind only: the underlying virtio-fs host-edge grant is added to the sandbox's policy-share allowlist with no access mode. The directory stays writable at its shared-export path, so unprivileged…
When was CVE-2026-18171 disclosed?
CVE-2026-18171 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18171 actively exploited?
CVE-2026-18171 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 98.8% of all scored CVEs.
What is the CVSS score of CVE-2026-18171?
CVE-2026-18171 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-18171?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18171, 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-18171

Explore →

Is Your Infrastructure Affected by CVE-2026-18171?

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