# CVE-2026-58096: ppp(8): missing length validation in LcpDecodeConfig()

> A malicious PPP peer can trigger an out-of-bounds write in the FreeBSD PPP daemon, potentially leading to arbitrary code execution as root or a system crash.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-92ww-f582-cp72

## What is CVE-2026-58096?

CVE-2026-58096 is a high-severity memory corruption vulnerability in Freebsd Freebsd, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LcpDecodeConfig() did not validate the length of received endpoint discriminator options against the minimum required by RFC 1717.  Undersized options would trigger an out-of-bounds write.

A malicious PPP peer can exploit CVE-2026-58095 and CVE-2026-58096 to crash ppp(8) or potentially execute arbitrary code as root.

Weakness: CWE-787 (Out-of-bounds Write), CWE-130 (Improper Handling of Length Parameter Inconsistency)

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

It affects 1 product.


Products: Freebsd Freebsd.

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

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

## Is CVE-2026-58096 being exploited?

There is no known exploitation of CVE-2026-58096 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-58096 and fix it if it is affected.

What it is: CVE-2026-58096 is a high-severity memory corruption vulnerability in Freebsd Freebsd, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58096 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-58096/ (Markdown: https://insights.sbomify.com/CVE-2026-58096/index.md)
```

## Sources

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

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