Skip to main content
Mallory
CriticalVulnerability

CVE-2026-87121: Remote Code Execution in lwIP MQTT Client

Published Sep 22, 2026 · Updated 27 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v4
EPSS0.78%56th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-87121CWE-787 · Out-of-bounds Write

CVE-2026-87121 is an out-of-bounds write vulnerability in the MQTT client implementation of the lwIP TCP/IP stack, affecting versions 2.0.1 through 2.2.1 inclusive. A remote, unauthenticated attacker may exploit the vulnerability to achieve full code execution on an affected device without user interaction. The vulnerability is rated Critical, with CVSS v3.1 and v4.0 scores of 9.8 and 9.3, respectively. The specific vulnerable function and triggering input are not identified.

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 may allow full code execution on the affected device, with high impacts to confidentiality, integrity, and availability. An attacker could potentially access sensitive device data, modify device behavior, or disrupt operation. Exploitation does not establish compromise of systems beyond the vulnerable device.

Mitigation

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

Minimize network exposure of affected devices and prevent direct internet accessibility of control systems. Place control-system networks and remote devices behind firewalls and isolate them from business networks. Where remote access is necessary, use secure, updated VPN solutions and assess the security of connected devices. Perform impact analysis and risk assessment before deploying defensive measures.

Remediation

Patch, then assume compromise.

Update lwIP to incorporate upstream fix commit f89407ea711879c04d91c92b35d67be78bbaf0f1. For embedded products, obtain and deploy a vendor firmware update incorporating this fix. A specific fixed release version is not identified.

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

Frequently asked questions

Is CVE-2026-87121 exploited in the wild?
As of Oct 23, 2026, Mallory has no reports of CVE-2026-87121 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-87121?
As of Oct 23, 2026, Mallory has found no public exploit for CVE-2026-87121.
Is there a patch for CVE-2026-87121?
Update lwIP to incorporate upstream fix commit f89407ea711879c04d91c92b35d67be78bbaf0f1. For embedded products, obtain and deploy a vendor firmware update incorporating this fix.
How severe is CVE-2026-87121?
CVE-2026-87121 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 0.78% (56th percentile) as of Oct 23, 2026.
Activity feed

Recent activity

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

View more in app →
+1 more in the timeline. Sign up to see them
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.