Loading vulnerability…
CVE-2026-49415 is a FreeBSD execve(2) race condition affecting execution of SUID-root binaries. During execve(2), the new virtual address space is installed before the process credentials are updated. In that window, another process running as the same user can access the target process memory through procfs or linprocfs. This creates a time-of-check/time-of-use condition in which an unprivileged local user can modify the address space of a SUID-root program before the credential transition completes, enabling takeover of the privileged process.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A FreeBSD execve-related local privilege escalation vulnerability affecting SUID root program handling under specific procfs/linprocfs conditions.
A local privilege escalation vulnerability in FreeBSD's execve handling that may permit elevation via SUID root binaries in specific procfs/linprocfs scenarios.
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.