CVE-2026-41568

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 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
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: 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 create empty files or directories at arbitrary absolute paths on the host filesystem. This issue has been patched in Docker Engine version 29.5.1 and Moby Daemon version 2.0.0-beta.14.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
1.4%
KEV
Not listed

Published

May 18, 2026

Last Modified

June 16, 2026

Advisory Details (1)

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

Race condition in docker cp allows creation of arbitrary empty files on the host via symlink swap · Advisory · moby/moby · GitHub

https://github.com/moby/moby/security/advisories/GHSA-vp62-88p7-qqf5

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/docker/docker
github.com/moby/moby
github.com/moby/moby/v22.0.0-beta.14

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-41568?
CVE-2026-41568 is a medium 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 create empty files or directories at arbitrary…
When was CVE-2026-41568 disclosed?
CVE-2026-41568 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-41568 actively exploited?
CVE-2026-41568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41568?
CVE-2026-41568 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-41568?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41568, 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-41568

Explore →

Is Your Infrastructure Affected by CVE-2026-41568?

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