SBOM for OT and ICS: What the Latest lwIP Advisories Teach Us About Component Visibility

SBOM for OT and ICS: What the Latest lwIP Advisories Teach Us About Component Visibility

SBOM for OT and ICS: What the Latest lwIP Advisories Teach Us About Component Visibility

SBOM for OT and ICS
Shieldworkz Logo

Team Shieldworkz

On September 22, 2026, CISA published two advisories for lwIP, the open-source TCP/IP stack found inside a very large number of embedded and industrial devices. One flaw in the MQTT client scores 9.8 and can lead to code execution. 

The harder question for an asset owner is not how severe the flaw is. It is: do we run any device that contains this library, and how would we know? 

Most OT teams cannot answer that quickly. Device names and IP addresses sit in the asset inventory. The libraries compiled into the firmware do not. That gap is the case for an SBOM for OT, and lwIP shows it clearly. 

What CISA published on lwIP 

Here is what is on record as of this writing. 

ICSA-26-265-01 (CVE-2026-87121): out-of-bounds write in the MQTT client 

  • The advisory says the flaw is an out-of-bounds write that may allow full code execution on the device, and lists affected versions as 2.0.1 through 2.2.1.

  • The CVSS v3.1 score is 9.8 (vector AV:N/AC:L/PR:N/UI:N), and the CVSS v4.0 score is 9.3.

  • CISA points users to the upstream lwIP repository, with a named fix commit.

  • The finder credited in the CVE record is Shahriyar Jalayeri of ByteRay Ltd.

ICSA-26-265-02 (CVE-2026-91018): double free in the lwIP API 

  • It is a double free (CWE-415) affecting lwIP API versions 2.0.1 through 2.2.1, reported by Eric Evenchick of Tetrel Security.  

  • Adjacent-network attackers can crash lwIP-based devices or corrupt memory in a way that may lead to arbitrary code execution.

  • The CVSS v4 base score is 8.7 with an adjacent attack vector.

Earlier lwIP issue worth tracking: CVE-2026-8836 

  • This is a stack-based overflow in the SNMPv3 USM handler (snmp_parse_inbound_frame), published in May 2026, with a CVSS v4 score of 8.9.

  • If your devices ship the lwIP SNMP agent, this belongs in the same review. 

Exploitation status. At the time of the tracker data I reviewed, CVE-2026-87121 was not on CISA’s KEV list and active exploitation had not been confirmed, with an EPSS score of 0.5% as of mid-October. Another source also listed no public exploit. That is a reason to prioritise, not a reason to wait. Check these figures again before you act, because they change.

Distribution status. Debian trackers listed the affected lwip source package as having no fix for stable releases when I checked. Upstream fixes and downstream firmware fixes are different things, and the second usually arrives much later.


Why lwIP is the right example for SBOM for OT 

lwIP is lightweight, permissively licensed and easy to port, so it ends up inside firmware from many suppliers. It is typically compiled into an RTOS or an MCU vendor SDK, and then into the final product. A PLC, an RTU, a gateway, a protocol converter and a smart sensor from different vendors can all carry it, and none of them will list “lwIP” on the datasheet. 

Three practical consequences follow: 

  1. The advisory names a component, not a product. One security write-up put it plainly: the listed range describes the vulnerable upstream component, not a complete catalogue of vulnerable products. Someone has to map component to product.  

  2. Being affected is not the same as being exploitable. The same write-up notes that the advisory does not prove that every device containing those versions permits reliable code execution. Whether the MQTT client is compiled in, enabled and reachable decides your real risk. That is the job of VEX, covered below.

  3. You cannot patch what you cannot see. This is the same lesson as Ripple20 in 2020, when a widely embedded TCP/IP stack turned into a supply-chain inventory problem across industries. The stack was different. The visibility failure was the same. 

What an OT-grade SBOM should contain 

An IT SBOM built from a package manifest often misses embedded components in firmware. For OT and ICS, aim for the following. 

  • Component identity: supplier, name, version, and a unique identifier such as a PURL or CPE. For lwIP, record the exact version or commit, since forks and vendor patches are common. 

  • Build-time configuration: which modules are compiled in (MQTT, SNMP, DHCP, IPv6) and which are off. For lwIP this is the difference between exposed and not exposed. 

  • Dependency relationships: lwIP inside the RTOS inside the SDK inside the firmware image. 

  • Hashes, licence and provenance data: CISA’s 2026 minimum elements add component hash algorithms, licences, the SBOM generation tool name and generation context.

  • Integrity: the guidance also adds a digital signature field so recipients can check an SBOM is genuine and unaltered.

  • Firmware-level coverage: binary analysis for devices where source is not available, since suppliers rarely hand over source code. 

Formats. CycloneDX and SPDX are both widely accepted. One CRA guide points to CycloneDX 1.6 or SPDX 3.0.1 and the ten BSI data fields, while noting no Commission implementing act on SBOM format has been adopted. Choose one, make it machine-readable, and keep it tied to your release process. 

SBOM plus VEX: from “affected” to “act on this” 

An SBOM tells you what is inside. A Vulnerability Exploitability eXchange (VEX) statement tells you whether a given vulnerability matters in that product. For lwIP, a supplier could say: 

  • “Product X contains lwIP 2.1.3, but the MQTT client is not compiled in. Not affected by CVE-2026-87121.” 

  • “Product Y contains lwIP 2.2.0 with MQTT enabled. Affected. Fixed firmware in version 4.2.” 

Without VEX, every lwIP advisory becomes a spreadsheet of false positives, and OT teams, who cannot patch quickly, will stop trusting the output. 

The regulatory clock: why this is no longer optional 

EU Cyber Resilience Act (CRA) 

  • The CRA entered into force on 10 December 2024, the reporting obligation applies from 11 September 2026, and the regulation applies in full from 11 December 2027.

  • Under Article 14, an actively exploited vulnerability must be reported within 24 hours as an early warning to the responsible national CSIRT and ENISA, followed by an update within 72 hours and a final report. The final report is due within 14 days of a fix becoming available.

  • Reporting duties also reach products already on the market.

  • The SBOM must exist and sit in the technical documentation, and be produced to market surveillance on request. It does not have to be published.

The practical point, made well by one CRA analysis, is that identifying active exploits in third-party components within 24 hours requires a maintained SBOM, even though the formal SBOM documentation duty starts in December 2027. A manufacturer shipping lwIP in an EU-bound product cannot run a 24-hour clock without knowing it ships lwIP.

US guidance. CISA, the NSA, the FBI and international partners released the 2026 Minimum Elements for a Software Bill of Materials, dated July 29, 2026, replacing the 2021 NTIA baseline. It applies the minimum elements to SBOMs for all software.

If you are an asset owner and not a manufacturer, the CRA does not bind you directly. It does change what you can ask for. Suppliers placing products on the EU market now have a legal reason to hand over component data, so put it in your contracts.


A response playbook for the next lwIP-style advisory 

  1. Triage by exposure, not by score. A 9.8 on a network-reachable MQTT client matters more in a DMZ gateway than in a sealed cell. An adjacent-network flaw like CVE-2026-91018 matters most on flat Layer 2 segments. 

  2. Query your SBOM store. Search for the component and the version range (2.0.1 to 2.2.1 here). Include hardware from integrators and OEMs. 

  3. Ask suppliers for a VEX statement where you have no SBOM. Ask specifically whether the affected module is compiled in and enabled. 

  4. Apply compensating controls while firmware is pending: segment, restrict MQTT brokers to known peers, limit SNMP exposure, and alert on unexpected traffic. Baselining expected TCP/IP traffic per device and alerting on new sources on the segment is a sensible start. 

  5. Track fixes at the right layer. Upstream commit, SDK release, device firmware, then your deployment. Record the status of each. 

  6. Feed lessons back into procurement. Make SBOM and VEX delivery a contract requirement. 

Common mistakes 

  • Treating the SBOM as a one-time deliverable instead of a living record tied to each release. 

  • Collecting SBOMs but not linking them to the asset inventory, so no one can query “which sites run this?” 

  • Counting “listed in an SBOM” as “vulnerable”, which creates alert fatigue without VEX. 

  • Ignoring forks and vendor-modified libraries that do not match upstream version numbers. 

  • Skipping legacy devices because “they can’t be scanned”. Those are often the ones most in need of supplier statements. 

How Shieldworkz helps 

Shieldworkz delivers end-to-end OT cybersecurity as a combined set of services, platform and solutions. For SBOM and component risk, that typically means: 

  • OT asset discovery and inventory that connects devices to firmware and component data 

  • Supplier SBOM and VEX intake and review, so the data is usable and not just filed 

  • Vulnerability prioritisation for OT, weighing exposure and process impact, not only CVSS 

  • Compensating-control design and segmentation for devices that cannot be patched quickly 

  • CRA and IEC 62443 readiness assessments for manufacturers and asset owners 

If a lwIP-style advisory landed tomorrow, could you list every affected device within a day? If not, that is the place to start. Talk to the Shieldworkz team about an OT component-visibility assessment. 

FAQ 

What is an SBOM for OT? 
A software bill of materials for OT is a machine-readable inventory of the software components inside industrial devices and systems, including firmware, RTOS and embedded libraries such as lwIP. 

Is lwIP vulnerable right now? 
Versions 2.0.1 through 2.2.1 are listed as affected by CVE-2026-87121 and CVE-2026-91018. Whether a specific product is exploitable depends on which modules it compiles in and how it is deployed. 

Does the CRA require an SBOM? 
Yes, as part of technical documentation, applying from 11 December 2027. Article 14 reporting has applied since 11 September 2026, and in practice it needs the same component data. 

What is the difference between SBOM and VEX? 
An SBOM lists components. VEX states whether a vulnerability actually affects a particular product. 

Does CISA require SBOMs for ICS? 
CISA publishes guidance (the 2026 Minimum Elements) and issues ICS advisories. It does not, by itself, mandate SBOMs for every ICS owner. Requirements come from regulation, contracts and procurement. 

Additional resources      

IEC 62443 - Practical guide for OT/ICS & IIoT security here
Remediation Guides here 
Guide to OT Asset Inventory and Device Management for Improved Security here
ICS Security Awareness Training Kit for Operators here
Cyber Risk Management Checklist here

احصل على تحديثات أسبوعية

الموارد والأخبار

تعرف على كيفية معالجة حلولنا الرائدة في مجال أمن تكنولوجيا التشغيل (OT) للتحديات الأمنية الحيوية

قد تود أيضًا

BG image

ابدأ الآن

عزز موقفك الأمني لنظام CPS

تواصل مع خبرائنا في أمن CPS للحصول على استشارة مجانية.

BG image

ابدأ الآن

عزز موقفك الأمني لنظام CPS

تواصل مع خبرائنا في أمن CPS للحصول على استشارة مجانية.

BG image

ابدأ الآن

عزز موقفك الأمني لنظام CPS

تواصل مع خبرائنا في أمن CPS للحصول على استشارة مجانية.