All vulnerabilities

Servers and applications

CVE-2026-92543

Docker Engine insecure-registry fallback via malicious DNS responses

Severity
High 7.6
Published
1 Oct 2026
Last changed
7 Oct 2026
Added to UpHeron
22 Oct 2026
Fixed in
v2.0.0-beta.25, 2.0.0-beta.25, 29.8.2
Exploit chance
under 0.1% in the next 30 daysEPSS by FIRST, 19 Nov 2026
Weakness
Improper certificate validation (CWE-295)Cleartext transmission (CWE-319)
Attack
Over the network · Only under certain conditions · No login needed · Needs someone to view a page or file
Attacker can
Read data · Change data
CVSS vector
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
Also known as
GHSA-7cfq-22r6-qp73
Sources
CVE Program, Project advisories (GitHub)

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 resolved 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.

Disclosure of registry credentials sent via X-Registry-Auth to an attacker-controlled host with an invalid certificate, or substitution of a trusted image tag with attacker-controlled manifest and layers in image store.

From moby/moby's security advisory.

Workarounds

If upgrading is not immediately possible, ensure that registry hostnames resolve only to trusted, non-loopback IP addresses. For example, administrators can use a trusted DNS configuration or a local hosts-file entry to pin the registry hostname to its expected address.

Alternatively, restrict outbound network access from the Docker daemon so that registry connections can only reach trusted registry endpoints.

Removing entries from the insecure-registries configuration is not sufficient, because Docker Engine automatically treats the 127.0.0.0/8 and ::1/128 ranges as insecure.

Workarounds as given by moby/moby's security advisory.

Affected software

SoftwareAffected versions
Docker EngineServers and applications · cna:moby|moby
  • Every version before v2.0.0-beta.25
Docker EngineServers and applications · github:moby/moby
  • Every version before 2.0.0-beta.25
  • Every version before 29.8.2

About Docker Engine

open-source software for deploying and running of containerized applications

From Wikidata, CC0 1.0.
Developers building daily
20M+Docker
Docker Hub pulls
3,670,111,162Docker Hub, 15 Nov 2026
GitHub stars
72,264GitHub, 15 Nov 2026
Forks
19,314GitHub, 15 Nov 2026
Latest release
docker-v29.9.3GitHub, 15 Nov 2026
Released
3 Nov 2026GitHub
Developer
Docker, Inc.Wikidata
License
proprietary license, Apache Software License 2.0Wikidata
Written in
GoWikidata
First released
14 Mar 2013Wikidata
First published on GitHub
18 Jan 2013GitHub

Release lines

ReleaseLatestSecurity fixes
2929.9.3Yes
2828.5.2Ended 13 May 2026
2727.5.1Ended 3 May 2025
26.126.1.5Ended 17 Feb 2025
26.026.0.2Ended 8 Jun 2024
25.025.0.18Until 4 Dec 2026

From endoflife.date.

References