All reports
High

github.com/moby/moby: Docker Engine: Certificate verification bypass via flawed registry DNS check

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-92543

Probability of exploitation in the next 30 days: 0.09%

FIRST EPSS · 2026-11-19

Description

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.

A flaw was found in Docker Engine. This vulnerability can lead to information disclosure or container image tampering by allowing an attacker to intercept unencrypted registry traffic. The flaw exists because the engine disables Transport Layer Security (TLS) certificate verification if any resolved address of a registry hostname matches a trusted local loopback network. A remote attacker capable of manipulating Domain Name System (DNS) responses can inject a loopback address alongside an external server address, tricking the client into connecting to an attacker-controlled registry over insecure HTTP.