Loading vulnerability…
CVE-2026-49426 is a FreeBSD ptrace-related auditing flaw in which system calls executed through ptrace(PT_SC_REMOTE) can be logged with an incorrect result. When auditing a remotely executed system call via ptrace, the kernel passed the return value of an internal setup function to the audit exit-recording path rather than the actual return value of the executed system call. As a result, audit records could indicate that a traced system call succeeded even when the actual system call failed. The issue affects the integrity and accuracy of audit trails associated with ptrace-mediated debugging activity rather than directly enabling memory corruption or code execution.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A FreeBSD ptrace access-control vulnerability that may allow bypass of debugging restrictions.
A FreeBSD ptrace vulnerability that can weaken or bypass intended tracing restrictions.
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.