{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-92543", "assignerOrgId": "686469e6-3ff6-451b-ab8b-cf5b9e89401e", "state": "PUBLISHED", "assignerShortName": "Docker", "dateReserved": "2026-09-16T13:00:33.499Z", "datePublished": "2026-10-07T16:44:21.237Z", "dateUpdated": "2026-10-07T20:31:28.770Z"}, "containers": {"cna": {"affected": [{"defaultStatus": "unaffected", "product": "Docker Engine", "vendor": "Docker", "versions": [{"version": "0", "status": "affected", "lessThan": "29.8.2", "versionType": "semver"}]}, {"defaultStatus": "unaffected", "packageName": "github.com/moby/moby/v2", "product": "Moby", "vendor": "Moby", "versions": [{"version": "0", "status": "affected", "lessThan": "v2.0.0-beta.25", "versionType": "semver"}]}], "credits": [{"lang": "en", "type": "finder", "value": "Adam Korczynski of ADA Logics"}], "descriptions": [{"lang": "en", "value": "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."}], "impacts": [{"descriptions": [{"lang": "en", "value": "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."}]}], "metrics": [{"cvssV4_0": {"version": "4.0", "vectorString": "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", "baseScore": 7.6, "baseSeverity": "HIGH", "attackVector": "NETWORK", "attackComplexity": "HIGH", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "userInteraction": "PASSIVE", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "subAvailabilityImpact": "NONE", "Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "valueDensity": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "exploitMaturity": "NOT_DEFINED"}, "format": "CVSS", "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "problemTypes": [{"descriptions": [{"cweId": "CWE-295", "description": "CWE-295: Improper Certificate Validation", "lang": "en", "type": "CWE"}]}, {"descriptions": [{"cweId": "CWE-319", "description": "CWE-319: Cleartext Transmission of Sensitive Information", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "686469e6-3ff6-451b-ab8b-cf5b9e89401e", "shortName": "Docker", "dateUpdated": "2026-10-07T18:27:34.058Z"}, "references": [{"tags": ["vendor-advisory"], "url": "https://github.com/moby/moby/security/advisories/GHSA-7cfq-22r6-qp73"}], "title": "Docker Engine insecure-registry fallback via malicious DNS responses", "workarounds": [{"lang": "en", "value": "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. Using a trusted CA certificate for the registry does not mitigate this issue if the registry hostname can also resolve to a loopback address, because the resulting registry configuration permits connections without certificate verification. As a defense in depth against image substitution, images can be referenced by digest rather than by a mutable tag. This does not prevent disclosure of registry credentials and should not be considered a complete workaround."}]}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-10-07T20:31:15.802430Z", "id": "CVE-2026-92543", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-10-07T20:31:28.770Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-92543", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-10-07T20:31:15.802430Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-10-07T20:31:22.747Z"}}], "cna": {"title": "Docker Engine insecure-registry fallback via malicious DNS responses", "credits": [{"lang": "en", "type": "finder", "value": "Adam Korczynski of ADA Logics"}], "impacts": [{"descriptions": [{"lang": "en", "value": "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."}]}], "metrics": [{"format": "CVSS", "cvssV4_0": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 7.6, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "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", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "PASSIVE", "attackComplexity": "HIGH", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "affected": [{"vendor": "Docker", "product": "Docker Engine", "versions": [{"status": "affected", "version": "0", "lessThan": "29.8.2", "versionType": "semver"}], "defaultStatus": "unaffected"}, {"vendor": "Moby", "product": "Moby", "versions": [{"status": "affected", "version": "0", "lessThan": "v2.0.0-beta.25", "versionType": "semver"}], "packageName": "github.com/moby/moby/v2", "defaultStatus": "unaffected"}], "references": [{"url": "https://github.com/moby/moby/security/advisories/GHSA-7cfq-22r6-qp73", "tags": ["vendor-advisory"]}], "workarounds": [{"lang": "en", "value": "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. Using a trusted CA certificate for the registry does not mitigate this issue if the registry hostname can also resolve to a loopback address, because the resulting registry configuration permits connections without certificate verification. As a defense in depth against image substitution, images can be referenced by digest rather than by a mutable tag. This does not prevent disclosure of registry credentials and should not be considered a complete workaround."}], "descriptions": [{"lang": "en", "value": "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."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-295", "description": "CWE-295: Improper Certificate Validation"}]}, {"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-319", "description": "CWE-319: Cleartext Transmission of Sensitive Information"}]}], "providerMetadata": {"orgId": "686469e6-3ff6-451b-ab8b-cf5b9e89401e", "shortName": "Docker", "dateUpdated": "2026-10-07T18:27:34.058Z"}}}, "cveMetadata": {"cveId": "CVE-2026-92543", "state": "PUBLISHED", "dateUpdated": "2026-10-07T20:31:28.770Z", "dateReserved": "2026-09-16T13:00:33.499Z", "assignerOrgId": "686469e6-3ff6-451b-ab8b-cf5b9e89401e", "datePublished": "2026-10-07T16:44:21.237Z", "assignerShortName": "Docker"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Docker Engine", "vendor": "Docker", "versions": [{"lessThan": "29.8.2", "status": "affected", "version": "0", "versionType": "semver"}]}, {"defaultStatus": "unaffected", "packageName": "github.com/moby/moby/v2", "product": "Moby", "vendor": "Moby", "versions": [{"lessThan": "v2.0.0-beta.25", "status": "affected", "version": "0", "versionType": "semver"}]}], "source": "security@docker.com"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}], "id": "CVE-2026-92543", "lastModified": "2026-10-08T20:46:35.260", "metrics": {"cvssMetricV40": [{"cvssData": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "HIGH", "attackRequirements": "PRESENT", "attackVector": "NETWORK", "availabilityRequirement": "NOT_DEFINED", "baseScore": 7.6, "baseSeverity": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "exploitMaturity": "NOT_DEFINED", "integrityRequirement": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "privilegesRequired": "NONE", "providerUrgency": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "userInteraction": "PASSIVE", "valueDensity": "NOT_DEFINED", "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "version": "4.0", "vulnAvailabilityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "source": "security@docker.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-92543", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-10-07T20:31:15.802430Z", "version": "2.0.3"}}]}, "published": "2026-10-07T17:17:02.727", "references": [{"source": "security@docker.com", "url": "https://github.com/moby/moby/security/advisories/GHSA-7cfq-22r6-qp73"}], "sourceIdentifier": "security@docker.com", "vulnStatus": "Awaiting Analysis", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-295"}, {"lang": "en", "value": "CWE-319"}], "source": "security@docker.com", "type": "Secondary"}]}

{"bugzilla": {"description": "github.com/moby/moby: Docker Engine: Certificate verification bypass via flawed registry DNS check", "id": "2547596", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2547596"}, "csaw": false, "cvss3": {"cvss3_base_score": "7.4", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N", "status": "draft"}, "cwe": "CWE-295", "details": ["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."], "name": "CVE-2026-92543", "package_state": [{"cpe": "cpe:/a:redhat:multicluster_engine", "fix_state": "Affected", "package_name": "multicluster-engine/assisted-service-9-rhel9", "product_name": "Multicluster Engine for Kubernetes"}, {"cpe": "cpe:/a:redhat:multicluster_globalhub", "fix_state": "Affected", "package_name": "multicluster-globalhub/multicluster-globalhub-grafana-rhel9", "product_name": "Multicluster Global Hub"}, {"cpe": "cpe:/a:redhat:acm:2", "fix_state": "Affected", "package_name": "rhacm2/acm-grafana-rhel9", "product_name": "Red Hat Advanced Cluster Management for Kubernetes 2"}, {"cpe": "cpe:/a:redhat:ceph_storage:5", "fix_state": "Affected", "package_name": "rhceph/rhceph-5-dashboard-rhel8", "product_name": "Red Hat Ceph Storage 5"}, {"cpe": "cpe:/a:redhat:ceph_storage:7", "fix_state": "Affected", "package_name": "rhceph/grafana-rhel9", "product_name": "Red Hat Ceph Storage 7"}, {"cpe": "cpe:/a:redhat:ceph_storage:9", "fix_state": "Affected", "package_name": "rhceph/grafana-rhel10", "product_name": "Red Hat Ceph Storage 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Affected", "package_name": "grafana", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Affected", "package_name": "grafana", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Affected", "package_name": "openshift4/ose-agent-installer-api-server-rhel8", "product_name": "Red Hat OpenShift Container Platform 4"}, {"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Affected", "package_name": "openshift4/ose-agent-installer-api-server-rhel9", "product_name": "Red Hat OpenShift Container Platform 4"}, {"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Affected", "package_name": "openshift4/ose-console", "product_name": "Red Hat OpenShift Container Platform 4"}], "public_date": "2026-10-07T16:44:21Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-92543\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-92543\nhttps://github.com/moby/moby/security/advisories/GHSA-7cfq-22r6-qp73"], "threat_severity": "Important"}