Loading vulnerability…
CVE-2026-41285 affects OpenBSD through 7.8. The vulnerability is in the slaacd and rad daemons' handling of ICMPv6 Neighbor Discovery (ND) options received from the local network. A crafted ND option with nd_opt_len set to zero can trigger an infinite loop because the code evaluates an expression of the form "nd_opt_len * 8 - 2" without first validating that nd_opt_len is non-zero. As a result, malformed IPv6 Neighbor Discovery traffic can cause the affected daemon to loop indefinitely while processing the packet.
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.
This repository is a small Python PoC for CVE-2026-41285, a local-link denial-of-service vulnerability in OpenBSD IPv6 Neighbor Discovery processing. The repo contains one README and two Python scripts under poc/. The main exploit, poc/kill_slaacd.py, uses Scapy to send a single Ethernet/IPv6 ICMPv6 Router Advertisement to the all-nodes multicast address ff02::1 with multicast MAC 33:33:00:00:00:01. The malicious condition is a raw ND option whose length byte is zero (bytes [200, 0]); according to the README, this triggers an integer underflow in userland ND option parsing inside slaacd (and similarly rad), causing an infinite loop and sustained CPU usage. The result is persistent loss of IPv6 SLAAC processing until manual daemon restart. The second script, poc/prove_dos.py, is a more operational demonstration harness. It uses Paramiko to SSH to a hardcoded OpenBSD target at 192.168.217.130 as root, restarts slaacd, checks current autoconfigured IPv6 addresses and CPU usage, sends a legitimate RA advertising 2001:db8:1::/64, then sends the exploit RA, and finally sends another legitimate RA for 2001:db8:2::/64 to prove the daemon no longer processes advertisements. It also performs cleanup by killing and restarting slaacd. This script demonstrates exploit impact rather than expanding capability beyond DoS. Overall, the exploit is a real, functional network-based local-segment DoS PoC, not a scanner or detection script. It is operational but not heavily weaponized: payloads and target values are mostly hardcoded, and exploitation requires same-L2 adjacency plus raw packet privileges.
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.