Loading vulnerability…
CVE-2026-50243 affects NLnet Labs Unbound from 1.6.2 through 1.25.1 when Unbound is configured with the respip module before the validator and uses either a response-ip redirect rule or an RPZ policy containing an RPZ-IP trigger. In this configuration, the rewriting handler fails to preserve and enforce the security status of the upstream DNS answer. If the validator determines that an A or AAAA answer is BOGUS because of an expired or otherwise invalid RRSIG, but the address matches the configured response-ip or RPZ rewrite range, Unbound still rewrites the answer to the operator-defined target and assigns it a hard-coded security state of INSECURE instead of returning SERVFAIL. This creates a DNSSEC validation bypass in the rewrite path, allowing invalid signed answers to be transformed into apparently acceptable insecure responses.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.