Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-56099: OpenBSD mpls_do_error Remote Kernel Stack Disclosure via MPLS Label Stack Over-read

Published Jun 18, 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.
CVSS6.9Medium · v4
EPSS0.50%44th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Openbsd
IdentifiersCVE-2026-56099CWE-125 · Out-of-bounds Read

CVE-2026-56099 is an out-of-bounds read in OpenBSD's MPLS error-handling path, specifically in mpls_do_error() in sys/netmpls/mpls_input.c. The function parses an incoming MPLS label stack into a fixed-size local array of 16 struct shim_hdr entries. If an attacker sends a crafted MPLS frame containing 16 labels with no Bottom-of-Stack (BoS) bit set, the parsing logic allows nstk to reach the maximum depth of 16. Subsequent code paths then compute a copy length of (nstk + 1) * sizeof(*shim), resulting in an attempted copy of 17 shim headers from a 16-entry local array. This causes a 4-byte over-read of adjacent kernel stack memory. The leaked data is then reflected back to the sender in the generated ICMP/MPLS error response. The vulnerable path is remotely reachable through mpls_input() -> mpls_do_error() on systems with MPLS enabled.

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 discloses 4 bytes of adjacent kernel stack memory per crafted packet. The leak is remote and repeatable, and the disclosed bytes are returned to the attacker in the ICMP/MPLS error response as an extra MPLS shim header. While the primitive is limited to a small disclosure per request, it exposes kernel memory contents and may aid bypass of kernel memory protections, debugging of kernel state, or chaining with other vulnerabilities.

Mitigation

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

Disable MPLS on exposed interfaces or disable MPLS entirely where not required. Filter or drop inbound MPLS traffic (EtherType 0x8847) from untrusted networks, especially on interfaces where remote parties can inject MPLS frames. As an interim measure, restrict network paths that can deliver MPLS packets to the host until the fixed kernel is deployed.

Remediation

Patch, then assume compromise.

Update OpenBSD to a version containing the 2026-06-18 fix commit 6a23123ec05f1eb29cfcaae0f3a468b2e1983cfd (mpls_input.c v1.82) or a later release that includes this change. The fix adds a guard that drops MPLS label stacks that reach MPLS_INKERNEL_LOOP_MAX without encountering a Bottom-of-Stack bit, preventing the out-of-bounds copy length from being used.

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-56099 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-56099 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-56099?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-56099.
Is there a patch for CVE-2026-56099?
Update OpenBSD to a version containing the 2026-06-18 fix commit 6a23123ec05f1eb29cfcaae0f3a468b2e1983cfd (mpls_input.c v1.82) or a later release that includes this change. The fix adds a guard that drops MPLS label stacks that reach MPLS_INKERNEL_LOOP_MAX without encountering a Bottom-of-Stack bit, preventing the out-of-bounds copy length from being used.
What products are affected by CVE-2026-56099?
Openbsd.
How severe is CVE-2026-56099?
CVE-2026-56099 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.50% (44th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

5 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 activity4Community discussion across Reddit, Mastodon, and other social sources.