{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92543 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92543 is a high-severity vulnerability in Docker Engine, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-92543 and fix it if it is affected.\n\nWhat it is: CVE-2026-92543 is a high-severity vulnerability in Docker Engine, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-92543 in the wild and no public exploit code.\n\nAffected product: Docker Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-92543/ (Markdown: https://insights.sbomify.com/CVE-2026-92543/index.md)","id":"CVE-2026-92543","markdown":"https://insights.sbomify.com/CVE-2026-92543/index.md","name":"CVE-2026-92543","record":{"aliases":["AZL-107195","AZL-107315","AZL-107333","AZL-107351","AZL-107748","BELL-CVE-2026-92543","DEBIAN-CVE-2026-92543","ECHO-d9ac-ee9e-fee7","GHSA-7cfq-22r6-qp73","MINI-4hgx-rm7p-9vx8","MINI-4pq5-2vgq-q5f7","MINI-6236-wxjh-fxj7","MINI-jj7j-cfrc-pwvh","OESA-2026-4657","UBUNTU-CVE-2026-92543"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Docker Engine","requires_auth":"none","summary":"Attackers can bypass TLS certificate verification for Docker registries by manipulating DNS responses to include a loopback address, enabling man-in-the-middle attacks.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-295","name":"Improper Certificate Validation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Docker Engine insecure-registry fallback via malicious DNS responses","id":"CVE-2026-92543","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Authentication Bypass with X-Agentic-Ally-Token in Keepnet Labs Agentic AI / Agentic Ally","id":"CVE-2026-92546"},"packages":[],"prev":{"headline":"Blind VXLAN injection into encrypted overlay networks from cluster peer","id":"CVE-2026-92542"},"products":["Docker Engine","Moby"],"published":"2026-10-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["Docker","Moby"]},"summary":"Attackers can bypass TLS certificate verification for Docker registries by manipulating DNS responses to include a loopback address, enabling man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2026-92543/"}