{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-40012 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-40012 is a medium-severity vulnerability in PowerDNS Recursor, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40012 and fix it if it is affected.\n\nWhat it is: CVE-2026-40012 is a medium-severity vulnerability in PowerDNS Recursor, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-40012 in the wild and no public exploit code.\n\nAffected product: PowerDNS Recursor. 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-40012/ (Markdown: https://insights.sbomify.com/CVE-2026-40012/index.md)","id":"CVE-2026-40012","markdown":"https://insights.sbomify.com/CVE-2026-40012/index.md","name":"CVE-2026-40012","record":{"aliases":["DEBIAN-CVE-2026-40012","GHSA-fmvv-f47m-6c7p","UBUNTU-CVE-2026-40012"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"PowerDNS Recursor","requires_auth":"none","summary":"Attackers can leak ECS zero scoped answers from the packet cache in PowerDNS Recursor when ECS is enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"OX","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-524","name":"Use of Cache Containing Sensitive Information"}],"description":"ECS zero scoped answers are stored in the packet cache while they should not. This impacts only configurations that have ECS enabled;","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":"Information about ECS zero scoped answers might leak to clients that use a specific ECS","id":"CVE-2026-40012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in OX Dovecot CE","id":"CVE-2026-40013"},"packages":[],"prev":{"headline":"Prometheus denial of service via crafted DNS queries","id":"CVE-2026-40011"},"products":["Recursor"],"published":"2026-06-25","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["PowerDNS"]},"summary":"Attackers can leak ECS zero scoped answers from the packet cache in PowerDNS Recursor when ECS is enabled.","url":"https://insights.sbomify.com/CVE-2026-40012/"}