Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-55706: Authentication Bypass in OpenBSD sppp_pap_input

Published Jun 17, 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.3High · v3.1
EPSS0.35%30th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Openbsd
IdentifiersCVE-2026-55706CWE-287

CVE-2026-55706 is an authentication bypass vulnerability in OpenBSD’s PPP stack affecting the PAP handling logic in sppp_pap_input() within sys/net/if_spppsubr.c. The vulnerable code uses bcmp() with comparison lengths derived directly from attacker-controlled PAP field lengths instead of first enforcing exact expected lengths. By supplying zero-length username and password fields, an attacker can cause both comparisons to evaluate as equal, resulting in successful PAP authentication without valid credentials. The same code path also contained a related heap over-read condition when an oversized name length caused bcmp() to read past the allocated buffer. The flaw was fixed by adding exact-length checks before comparison operations.

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 an attacker to bypass PAP authentication on affected OpenBSD systems. In PPPoE deployments, a rogue server on the same broadcast domain can authenticate a victim without knowing legitimate credentials, impersonate the expected access endpoint, and position itself to intercept or relay traffic. This can enable man-in-the-middle access to victim network communications. The related over-read condition may also expose kernel memory safety risk, although the primary documented security consequence is authentication bypass.

Mitigation

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

Until patched builds are deployed, reduce exposure by disabling or avoiding PAP where possible, preferring stronger PPP authentication methods that are not affected by this code path. Limit PPPoE access to trusted network segments, prevent untrusted or rogue PPPoE servers from operating on the same broadcast domain, and use network controls that restrict adjacent-layer attacker access. These measures only reduce exploitability and are not a substitute for applying the vendor fix.

Remediation

Patch, then assume compromise.

Update OpenBSD to a version that includes commit 076e2b1c1fc4ac0883a72d3544131ad5cee7adf8 or a later patched release. The fix adds exact-length validation before credential comparisons in the PAP handler and closes both the authentication bypass and the associated heap over-read condition.

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
OpenbsdOpenbsdoperating_system
FAQ

Frequently asked questions

Is CVE-2026-55706 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-55706 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-55706?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-55706.
Is there a patch for CVE-2026-55706?
Update OpenBSD to a version that includes commit 076e2b1c1fc4ac0883a72d3544131ad5cee7adf8 or a later patched release. The fix adds exact-length validation before credential comparisons in the PAP handler and closes both the authentication bypass and the associated heap over-read condition.
What products are affected by CVE-2026-55706?
Openbsd.
How severe is CVE-2026-55706?
CVE-2026-55706 has a CVSS v3.1 score of 8.3 (High) and an EPSS score of 0.35% (30th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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.