{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12539 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12539 is a medium-severity vulnerability in Docker Sandboxes, published on 18 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12539 and fix it if it is affected.\n\nWhat it is: CVE-2026-12539 is a medium-severity vulnerability in Docker Sandboxes, published on 18 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-12539 in the wild and no public exploit code.\n\nAffected product: Docker Sandboxes. 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-12539/ (Markdown: https://insights.sbomify.com/CVE-2026-12539/index.md)","id":"CVE-2026-12539","markdown":"https://insights.sbomify.com/CVE-2026-12539/index.md","name":"CVE-2026-12539","record":{"aliases":["GHSA-x6hr-f96v-hhgg"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Docker Sandboxes","requires_auth":"low_privilege","summary":"Attackers in Docker Sandboxes can bypass ICMP egress restrictions after daemon restarts to perform reconnaissance and exfiltrate data via ICMP covert channels.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"},{"id":"CWE-665","name":"Improper Initialization"}],"description":"Docker Sandboxes (sbx) blocks ICMP egress with an authorizer applied only at network-creation time, and does not re-apply it to networks rebuilt from disk when the Docker daemon restarts, so a restart-surviving sandbox forwards ICMP to arbitrary hosts. A workload inside a sandbox, which the threat model treats as untrusted, can therefore defeat the documented ICMP egress block to perform network reconnaissance and exfiltrate data over an ICMP covert channel, regardless of the configured allowlist.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Docker Sandboxes ICMP egress restriction bypass after daemon restart","id":"CVE-2026-12539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Foreman: command injection in foreman-rake errors:fetch_log via request_id parameter","id":"CVE-2026-12540"},"packages":[],"prev":{"headline":"Unauthenticated Remote Code Execution in Gemini CLI CI/CD Workflows","id":"CVE-2026-12537"},"products":["Docker Sandboxes"],"published":"2026-06-18","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":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["Docker"]},"summary":"Attackers in Docker Sandboxes can bypass ICMP egress restrictions after daemon restarts to perform reconnaissance and exfiltrate data via ICMP covert channels.","url":"https://insights.sbomify.com/CVE-2026-12539/"}