Skip to main content
VulnerabilityPublished

CVE-2026-92543: Docker Engine · Improper Certificate Validation

Affects Docker EngineSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 29.8.2 soon.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 29.8.2, v2.0.0-beta.25, 2.0.0-beta.25
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade Docker Engine to 29.8.2; Moby to v2.0.0-beta.25; github.com/moby/moby/v2 to 2.0.0-beta.25.

Affected software

ProductAffectedFixed in
DockerDocker EngineAffected
  • <29.8.2
Fixed in
  • 29.8.2
MobyMobyAffected
  • <2.0.0-beta.25
Fixed in
  • v2.0.0-beta.25
GitHubgithub.com/moby/moby/v2pkg:github/github.com/moby/moby/v2Other threatsAffected
  • <2.0.0-beta.25
Fixed in
  • 2.0.0-beta.25

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should be cautious about registry configurations and DNS responses to avoid exposure to this vulnerability.

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.

References

Community reviews

Loading reviews…