CVE-2026-41568

Host service interruption via symlink-swap race

Published Jun 12, 2026 · Updated Jun 12, 2026

TOCTOU race in Moby 28.5.2 and earlier and Moby v2 before 2.0.0-beta.14 allows attackers to create empty files or directories at arbitrary host paths. After GetResourcePath resolves a volume destination, createIfNotExists uses os.MkdirAll or os.OpenFile on that absolute path, so an in-container symlink swap redirects the root operation beyond the container filesystem. Exploitation requires a running container with a volume mount, rapid symlink replacement, and an operator-initiated docker cp or archive API request; the result is host service interruption without access to existing file contents.

CVSS severity6.1
Medium
EPSS probability0.11%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

TOCTOU race in Moby 28.5.2 and earlier and Moby v2 before 2.0.0-beta.14 allows attackers to create empty files or directories at arbitrary host paths. After GetResourcePath resolves a volume destination, createIfNotExists uses os.MkdirAll or os.OpenFile on that absolute path, so an in-container symlink swap redirects the root operation beyond the container filesystem. Exploitation requires a running container with a volume mount, rapid symlink replacement, and an operator-initiated docker cp or archive API request; the result is host service interruption without access to existing file contents.

The record

CVE
CVE-2026-41568
Published
Jun 12, 2026
Updated
Jun 12, 2026
Vendor
Moby Project
Product
Moby
Classifications
CWE-61, CWE-367, CWE-81, T1499
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Jun 12, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 12, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=Docker Engine < 29.5.1
  2. Affected versionversion=github.com/docker/docker/daemon <= 28.5.2
  3. Affected versionversion=github.com/moby/moby/v2/daemon < 2.0.0-beta.14

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

Moby Project · Mobyversion=Docker Engine < 29.5.1; version=github.com/docker/docker/daemon <= 28.5.2; version=github.com/moby/moby/v2/daemon < 2.0.0-beta.14

Published CVSS scores

6.1GitHub, Inc.CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-61UNIX Symbolic Link (Symlink) Following
CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
CWE-81Improper Neutralization of Script in an Error Message Web Page
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo