CVE-2026-92543

published 7 Oct 2026 · updated 13 Nov 2026

Docker Engine insecure-registry fallback via malicious DNS responses

7.6HighCVSS 7.6EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Engine 29.8.2 and v2.0.0-beta.25.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
DockerEngine<29.8.229.8.2
Moby<v2.0.0-beta.25v2.0.0-beta.25

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Docker, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-92543 severity on Zeptric[![CVE-2026-92543](https://zeptric.io/badge/cve/CVE-2026-92543.svg)](https://zeptric.io/cve/CVE-2026-92543)