Loading vulnerability…
CVE-2026-49430 is an integer-truncation vulnerability in OpenZFS's ZFS_IOC_RECV_NEW ioctl heal-receive path. A 64-bit receive-stream payload size is truncated to a 32-bit value when calculating an allocation, but the original 64-bit size is subsequently used as the length of a byteswap operation. This size mismatch can cause the byteswap operation to access or write beyond the allocated kernel buffer, resulting in kernel memory corruption.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A ZFS kernel-memory-corruption vulnerability in the ZFS_IOC_RECV_NEW ioctl heal receive path. A crafted receive stream can cause a 64-bit payload length to be truncated to 32 bits for allocation while the original 64-bit length is used in a byteswap operation; a local user holding delegated ZFS receive permission can trigger the corruption.
An OpenZFS vulnerability related to handling of the '$hasrecvd' property.
An OpenZFS vulnerability in FreeBSD related to handling of the "$hasrecvd" property; the notice says it is not considered dangerous.
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.