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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An out-of-bounds write in ppp(8)'s LcpDecodeConfig() caused by inadequate validation of received endpoint discriminator option lengths. A malicious PPP peer may crash ppp(8) or potentially achieve arbitrary code execution with root privileges.
Critical memory-safety vulnerability in FreeBSD ppp(8) that a malicious PPP peer could potentially exploit to execute arbitrary code as root or crash the service.
An out-of-bounds write in FreeBSD ppp(8), caused by inadequate validation of received multilink endpoint discriminator option lengths. A malicious PPP peer may cause a crash or potentially execute code as root.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.