Out-of-bounds write flaw in lwIP MQTT client
An out-of-bounds write in lwIP's MQTT client (versions 2.0.1-2.2.1) could let an attacker achieve full code execution on affected embedded devices; no known exploitation in the wild.
Sourcecisa.gov — open the original
What to check
- Applies to
- The 1 CVE named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
CISA has published an ICS advisory for a vulnerability in the MQTT Client Application component of the lwIP TCP/IP stack, a widely embedded networking library used across critical infrastructure sectors including chemical, communications, critical manufacturing, energy, financial services, healthcare, transportation, and water/wastewater. The vulnerability, tracked as CVE-2026-87121 and classified as CWE-787 (Out-of-bounds Write), affects lwIP MQTT Client versions >=2.0.1 and <=2.2.1. Successful exploitation could allow an attacker to achieve full code execution on the affected device, which is significant given lwIP's broad deployment in embedded and IoT/ICS devices worldwide.
The vulnerability was reported to CISA by Shahriyar Jalayeri of ByteRay Ltd. CISA states no known public exploitation specifically targeting this vulnerability has been reported at this time. A fix is available upstream via the lwIP repository on Savannah, identified by commit f89407ea711879c04d91c92b35d67be78bbaf0f1.
Defenders and device manufacturers using lwIP's MQTT client should update to the patched version referencing the fix commit. Standard ICS network hardening practices apply: minimize internet exposure of control system devices, isolate control networks behind firewalls, and use VPNs with up-to-date patching for any required remote access. Given the wide deployment of lwIP embedded in numerous vendor products, asset owners should inventory devices for use of this library and coordinate patching with device vendors.
Mentioned in this report
Detection guidance
1 detection for this report is in the app — an indicator rule with Sigma, Splunk SPL, Elastic, Microsoft Defender XDR KQL, and YARA. Free account, no card.
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-26-265-01
Free public brief. The indicators and the detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), and live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,445 reports from 149 sources, 666 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs