Docker · Docker Engine (Moby) · published 2026-10-07

CVE-2026-92543Docker Engine insecure-registry fallback via malicious DNS responses

Routine No exploitation evidence; EPSS 0.1%.

CVE-2026-92543 is not known to be exploited in the wild. EPSS estimates a 0.09% chance of exploitation in the next 30 days, higher than 0% of all CVEs. This Docker Engine (Moby) vulnerability: CVSS 7.6 (v4.0), a successful attack gives total control of the component. Fixed upstream in Docker Engine (Moby) 29.8.2, 25.0.19; Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Docker Engine (Moby) 29.8.2, 25.0.19.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixiedocker.ioWon’t fix
12 bookwormdocker.ioNo fix yet
Ubuntu (+1 more packages)26.04 LTSdocker.ioNo fix yet
Red Hat Enterprise LinuxRHEL 10grafanaNot affected
RHEL 9grafanaNot affected

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. This monthSecurity release

    Container runtimeDocker Engine (Moby)

    Docker Engine (Moby) security releases: 29.8.2, 25.0.19

    Upgrade to 29.8.225.0.19

    Why: Vendor security release for server software (most severe: CVE-2026-92543).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.1% (0th pct)FIRST EPSS v2026.06.15
CVSS base score7.6 (v4.0)
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Docker Engine classifies a registry hostname as insecure using an any-match DNS check. loadInsecureRegistries() injects 127.0.0.0/8 and ::1/128 as insecure CIDRs by default. isCIDRMatch resolves all of the hostname's addresses and returns true if a single address is in the insecure CIDR list. Because the transport re-dials the hostname rather than the CIDR-matching address, a DNS answer set of one loopback IP plus a non-loopback attacker IP disables certificate verification and enables HTTP fallback for the registry connection.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →