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

> Attackers can generate misleading audit records for ptrace syscalls, undermining audit-based intrusion detection systems on FreeBSD.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 26 Aug 2026

## What is CVE-2026-49426?

CVE-2026-49426 is a low-severity vulnerability in Freebsd Freebsd, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When auditing a system call executed via ptrace(PT_SC_REMOTE), the kernel passed the return value of an internal setup function to AUDIT_SYSCALL_EXIT() rather than the actual result of the executed system call.  As a result, committed audit records for system calls which returned an error do not reflect the true outcome of the operation.  That is, they indicate that the operation succeeded when it in fact failed.

Audit records for system calls executed via ptrace(PT_SC_REMOTE) may show an incorrect error status.  An attacker with the ability to debug a process could use this to produce misleading audit trails, potentially undermining audit-based Intrusion Detection Systems (IDS).

Weakness: CWE-224 (Obscured Security-relevant Information by Alternate Name), CWE-223 (Omission of Security-relevant Information)

## Which versions are affected by CVE-2026-49426?

It affects 1 product.


Products: Freebsd Freebsd.

## How do I fix CVE-2026-49426?

No fix has been published for CVE-2026-49426 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49426 being exploited?

There is no known exploitation of CVE-2026-49426 in the wild and no public exploit code.

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49426 and fix it if it is affected.

What it is: CVE-2026-49426 is a low-severity vulnerability in Freebsd Freebsd, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49426 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49426/ (Markdown: https://insights.sbomify.com/CVE-2026-49426/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49426
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49426
- OSV: https://osv.dev/vulnerability/CVE-2026-49426

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49426/
Summaries are generated and may contain mistakes; the official description above is the record.