EngineApplication · Docker
CVE-2026-41568
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMoby 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA race condition in Docker/Moby daemon's docker cp mount setup allows a malicious container to create empty files or directories at arbitrary absolute paths on the host filesystem, enabling local privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
EngineApplication
< 29.5.1<= 28.5.2= 2.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Docker Engine versionRun 'docker --version' or 'dockerd --version' to identify the installed Docker Engine version. Compare against the affected range: versions below 29.5.1 are vulnerable.Affected if Docker Engine version is below 29.5.1 (for example, 29.0.0 through 29.5.0)
-
Check Moby daemon versionRun 'moby --version' or check the moby daemon package version if using Moby instead of Docker Engine. Compare against the affected ranges: <= 28.5.2 or version 2.0.0.Affected if Moby version is 28.5.2 or lower, or exactly 2.0.0
-
Verify docker cp is accessible to containersReview container configurations and RBAC policies to determine whether untrusted containers have access to the docker cp command or docker socket. Check for any mounted docker.sock or docker CLI access.Affected if Untrusted or user-facing containers can execute docker cp or have access to the Docker socket
-
Audit host filesystem for suspicious empty filesSearch the host filesystem for newly created empty files or directories at unexpected absolute paths, particularly outside normal container working directories. Use 'find / -type f -size 0 -mtime recent' or similar to identify recently created zero-byte files.Affected if Empty files or directories exist at absolute paths on the host that were not created by legitimate docker operations
Your environment is affected if you run Docker Engine below 29.5.1 or Moby at version 28.5.2 or 2.0.0, and untrusted containers can access docker cp or the Docker socket, or if you find unexpected empty files at arbitrary host paths.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped29.5.1
Upgrade Docker Engine to version 29.5.1 or later, or Moby Daemon to version 2.0.0-beta.14 or later. In the interim, restrict container permissions and monitor for suspicious file creation activity.
Docker Engine >= 29.5.1 OR Moby Daemon >= 2.0.0-beta.14
- Check the current Docker Engine or Moby version using `docker version` or `moby version`
- Stop the Docker or Moby daemon service
- Upgrade Docker Engine to version 29.5.1 or later, or Moby Daemon to version 2.0.0-beta.14 or later
- Restart the Docker or Moby daemon service
- Verify the new version is running with `docker version` or `moby version`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Engine
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41568 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41568 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data