CVE-2026-42306

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under NVD CVSS v3. 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, nvd
Trending — 3 sources updated this week
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.2Exploit: NoneExposed: 0

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

Moby is an open source container framework. In Docker Engine prior to version 29.5.1, Docker Daemon versions 28.5.2 and prior, and Moby Daemon prior to version 2.0.0-beta.14, a race condition during docker cp mount setup allows a malicious container to redirect a bind mount target to an arbitrary host path, potentially overwriting host files or causing denial of service. This issue has been patched in Docker Engine version 29.5.1 and Moby Daemon version 2.0.0-beta.14.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity72% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
1.2%
KEV
Not listed

Published

May 18, 2026

Last Modified

June 16, 2026

Advisory Details (1)

Auto-updated Jun 12, 2026
Patch available. Sources: github.
github Patch Available

Race condition in docker cp allows bind mount redirection to host path · Advisory · moby/moby · GitHub

https://github.com/moby/moby/security/advisories/GHSA-rg2x-37c3-w2rh

Vendor Advisories for CVE-2026-42306(1)

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

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/docker/docker———
github.com/moby/moby———
github.com/moby/moby/v2—2.0.0-beta.14—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× 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-07-23 03:11 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-18 00:29 UTCOSV refresh
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-24 14:05 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
Show 10 more
  1. 2026-06-22 14:25 UTCEPSS rescore
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-17 17:53 UTCEPSS rescore
  7. 2026-06-15 17:49 UTCEPSS rescore
  8. 2026-06-13 23:00 UTCEPSS rescore
  9. 2026-06-12 23:12 UTCEPSS rescore
  10. 2026-05-24 06:16 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-42306?
CVE-2026-42306 is a high vulnerability published on May 18, 2026. Moby is an open source container framework. In Docker Engine prior to version 29.5.1, Docker Daemon versions 28.5.2 and prior, and Moby Daemon prior to version 2.0.0-beta.14, a race condition during docker cp mount setup allows a malicious container to redirect a bind mount target to an arbitrary…
When was CVE-2026-42306 disclosed?
CVE-2026-42306 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on June 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-42306 actively exploited?
CVE-2026-42306 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42306?
CVE-2026-42306 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-42306?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42306, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42306

Explore →

Is Your Infrastructure Affected by CVE-2026-42306?

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

Start Free Scan →Browse All CVEs