{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-42389 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-42389 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-42389 and fix it if it is affected.\n\nWhat it is: CVE-2026-42389 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-42389 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-42389/ (Markdown: https://insights.sbomify.com/CVE-2026-42389/index.md)","id":"CVE-2026-42389","markdown":"https://insights.sbomify.com/CVE-2026-42389/index.md","name":"CVE-2026-42389","record":{"aliases":["DEBIAN-CVE-2026-42389","GHSA-hrq7-vr6r-5mvq","UBUNTU-CVE-2026-42389"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"PowerDNS Recursor","requires_auth":"none","summary":"PowerDNS Recursor lacks sufficient validation of authoritative server answers, potentially allowing denial of service via invalid headers.","user_interaction":"not_required","vuln_class":"other"},"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:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"This fix provides extra hardening for the 5.4.x branch by doing extra validation of incoming answers from authoritative servers.","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":"Reject more queries with invalid header values","id":"CVE-2026-42389","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"ZONEMD validation can be bypassed","id":"CVE-2026-42390"},"packages":[],"prev":{"headline":"Missing input validation for catalog zones","id":"CVE-2026-42388"},"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":"PowerDNS Recursor lacks sufficient validation of authoritative server answers, potentially allowing denial of service via invalid headers.","url":"https://insights.sbomify.com/CVE-2026-42389/"}