{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-50243 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-50243 is a medium-severity vulnerability in Nlnetlabs Unbound, published on 22 Jul 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-50243 and fix it if it is affected.\n\nWhat it is: CVE-2026-50243 is a medium-severity vulnerability in Nlnetlabs Unbound, published on 22 Jul 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-50243 in the wild and no public exploit code.\n\nAffected product: Nlnetlabs Unbound. 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-50243/ (Markdown: https://insights.sbomify.com/CVE-2026-50243/index.md)","id":"CVE-2026-50243","markdown":"https://insights.sbomify.com/CVE-2026-50243/index.md","name":"CVE-2026-50243","record":{"aliases":["ALPINE-CVE-2026-50243","AZL-92988","DEBIAN-CVE-2026-50243","ECHO-47eb-2c54-a673","GHSA-vqq3-g95x-fpmr","UBUNTU-CVE-2026-50243"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"DNS resolver","requires_auth":"none","summary":"Attackers can bypass DNSSEC validation by spoofing BOGUS answers that are insecurely rewritten by response-ip or RPZ rules in Unbound.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NLnet Labs","cpe":[{"product":"unbound","vendor":"nlnetlabs"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-348","name":"Use of Less Trusted Source"}],"description":"In NLnet Labs Unbound 1.6.2 up to and including 1.25.1, when Unbound is configured with the 'respip' module in front of the validator together with a 'response-ip' redirect rule or an RPZ file with an RPZ-IP trigger, the rewriting handler does not check the security status of the upstream answer and can instead rewrite a BOGUS A/AAAA answer to point to an operator's configured IP. If the validator finds an expired or otherwise invalid RRSIG on an answer whose A record falls within a 'response-ip'/RPZ configuration, the answer is still rewritten and given a hard coded security level of INSECURE. This results in the client receiving an INSECURE NOERROR reply rewritten by the operator's configured IP. A malicious actor can exploit the possible poisonous effect by spoofing a BOGUS A/AAAA answer that falls inside the operator's configured subnet rewrites. Such DNSSEC protected answers are then insecurely redirected to the operator's configured target.","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":"'response-ip'/'rpz' can rewrite BOGUS answers instead of returning SERVFAIL","id":"CVE-2026-50243","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"nlnetlabs:unbound","products":["nlnetlabs:unbound"],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Naxclow IoT Platform Missing Authorization","id":"CVE-2026-50244"},"packages":[],"prev":{"headline":"Auth bypass in Hub","id":"CVE-2026-50242"},"products":["Unbound"],"published":"2026-07-22","related":[{"cvss_score":9.1,"headline":"Heap buffer overflow and possible Remote Code Execution when digesting DNSKEY","id":"CVE-2026-81642","kev_date_added":null,"published":"2026-09-16"},{"cvss_score":9.1,"headline":"Possible arbitrary code execution during DNSSEC validation","id":"CVE-2026-33278","kev_date_added":null,"published":"2026-05-20"},{"cvss_score":8.7,"headline":"Heap overflow with multiple NSID, COOKIE, PADDING EDNS options","id":"CVE-2026-42944","kev_date_added":null,"published":"2026-05-20"},{"cvss_score":8.7,"headline":"Crash during DNSSEC validation of malicious content","id":"CVE-2026-42959","kev_date_added":null,"published":"2026-05-20"},{"cvss_score":8.4,"headline":"CNAME synthesis could lead to heap corruption","id":"CVE-2026-82717","kev_date_added":null,"published":"2026-09-16"},{"cvss_score":7.5,"headline":"Possible heap buffer overflow during DNSSEC canonicalization","id":"CVE-2026-81634","kev_date_added":null,"published":"2026-09-16"},{"cvss_score":7.5,"headline":"Remote DNS-over-QUIC denial of service due to `quic-size` budget bypass","id":"CVE-2026-32665","kev_date_added":null,"published":"2026-07-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-07-22","vendors":["NLnet Labs"]},"summary":"Attackers can bypass DNSSEC validation by spoofing BOGUS answers that are insecurely rewritten by response-ip or RPZ rules in Unbound.","url":"https://insights.sbomify.com/CVE-2026-50243/"}