Loading vulnerability…
rldns (an open source DNS server) version 1.3 contains a heap-based out-of-bounds read condition that can be triggered to cause a denial of service. Version 1.4 includes a patch addressing the issue.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a minimal proof-of-concept DoS exploit for CVE-2026-27831 affecting rldns 1.3. Structure: (1) README.md describing the vulnerability (remote heap-based out-of-bounds read in rldns 1.3; patched in 1.4) and attribution; (2) exploit.c, a standalone C program that takes a target IPv4 address and UDP port, creates a UDP socket, and sends a single hardcoded 16-byte malformed DNS-like packet via sendto(). No shellcode, command execution, or persistence is present—capability is limited to remotely triggering a crash/service disruption on a vulnerable rldns instance listening on the specified UDP port.
2 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.