CVE-2026-49426: Incorrect audit records for ptrace(2) PT_SC_REMOTE syscall requests
- Vendor
- Freebsd
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.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows a user who can debug a process and invoke ptrace(PT_SC_REMOTE) to generate misleading audit records. This can undermine audit-based monitoring, incident detection, compliance evidence, and post-incident forensic reconstruction by causing failed remotely executed system calls to appear successful in audit logs. The primary security consequence is loss of trust in audit data and reduced reliability of security investigations.
Mitigation
If you can’t patch tonight, do this now.
No workaround is available. Systems that do not use audit(4) are not affected in practice, so disabling or not relying on the audit subsystem for affected tracing scenarios reduces exposure until patched.
Remediation
Patch, then assume compromise.
Upgrade FreeBSD to a corrected supported release level, including 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, or 14.3-RELEASE-p16, or apply the vendor patch for the audit subsystem issue and rebuild the affected kernel components as required, followed by a reboot.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-49426 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-49426 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-49426?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-49426.
- Is there a patch for CVE-2026-49426?
- Upgrade FreeBSD to a corrected supported release level, including 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, or 14.3-RELEASE-p16, or apply the vendor patch for the audit subsystem issue and rebuild the affected kernel components as required, followed by a reboot.
- What products are affected by CVE-2026-49426?
- Freebsd.
- How severe is CVE-2026-49426?
- CVE-2026-49426 has a CVSS v3.1 score of 3.3 (Low) and an EPSS score of 0.14% (3rd percentile) as of Sep 25, 2026.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.