Skip to main content
Mallory
LowVulnerability

CVE-2026-49426: Incorrect audit records for ptrace(2) PT_SC_REMOTE syscall requests

Published Aug 19, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS3.3Low · v3.1
EPSS0.14%3rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-49426CWE-778

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
FreebsdFreebsdoperating_system
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.