Skip to main content
Mallory
HighVulnerability

CVE-2026-58096: FreeBSD ppp(8) LcpDecodeConfig Endpoint Discriminator Out-of-Bounds Write

Published Aug 26, 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.
CVSS8.8High · v3.1
EPSS0.60%50th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-58096CWE-130 · Improper Handling of Length…

CVE-2026-58096 is an insufficient input-length validation vulnerability in FreeBSD ppp(8)'s LcpDecodeConfig() handling of received Multilink PPP endpoint discriminator options. The function does not verify that an endpoint discriminator option meets the minimum length required by RFC 1717 before processing it. A maliciously undersized option can therefore cause an out-of-bounds write.

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.

A malicious PPP peer can crash the ppp(8) process, causing a denial of service. Because ppp(8) executes with root privileges, successful exploitation may also permit arbitrary code execution as root.

Mitigation

If you can’t patch tonight, do this now.

No vendor workaround is available. Systems not using ppp(8) are not affected. Until updates can be installed, avoid operating ppp(8) where possible, restrict access to its command interface and the network group, and limit PPP connectivity to trusted peers.

Remediation

Patch, then assume compromise.

Upgrade to a supported and corrected FreeBSD stable or release/security branch dated after the applicable correction date. On supported amd64 or arm64 RELEASE installations, update FreeBSD base packages or apply binary operating-system updates using the supported FreeBSD update mechanism. Alternatively, apply the vendor source patch for the ppp(8) advisory, rebuild, and reinstall the operating system. Restart active ppp(8) instances or reboot after applying updates.

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-58096 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-58096 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-58096?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-58096.
Is there a patch for CVE-2026-58096?
Upgrade to a supported and corrected FreeBSD stable or release/security branch dated after the applicable correction date. On supported amd64 or arm64 RELEASE installations, update FreeBSD base packages or apply binary operating-system updates using the supported FreeBSD update mechanism.
What products are affected by CVE-2026-58096?
Freebsd.
How severe is CVE-2026-58096?
CVE-2026-58096 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.60% (50th 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 activity5Community discussion across Reddit, Mastodon, and other social sources.