CISA Flags libumqtt Integer Underflow with No Available Remediation

P1 — VALIDATE AND UPDATEHigh · 8.8 (CVSS v4.0); 8.6 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Find libumqtt 1.1.1 or earlier in deployed products, assess reachable MQTT processing, and obtain supplier guidance while restricting unnecessary exposure.

Confirm Scope And Apply The Supported Remediation

What to do now: Review dependency inventories, firmware components and SBOMs for libumqtt, then identify product owners and actual network data paths. Confirm the embedded version and whether untrusted traffic can reach the affected library. Do not assume all MQTT implementations use libumqtt. Contact the project or integrating vendor for supported remediation. Apply CISA’s network-exposure and segmentation guidance as appropriate after operational impact analysis. Record vendor responses, compensating controls and residual-risk decisions; validate connectivity and availability monitoring without sending malformed traffic to production systems.

Open the authoritative advisory

Last verified: 2026-11-19 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopelibumqtt MQTT client library
AdvisoryICSA-26-323-03
CVECVE-2026-125132
Authoritative release date2026-11-19 — displayed CISA release date; the page release metadata is 2026-11-19T12:00:00Z.
Authority revision dateCISA revision history records revision 1, Initial Publication, on November 19, 2026.
Affected versionslibumqtt 1.1.1 and earlier; a remotely reachable integer-underflow path can cause denial of service, memory corruption or information disclosure.
Fixed versionNo remediation is available in the CISA advisory; contact the libumqtt repository owners or the integrating product supplier for support.
CVSS base score8.8 (CVSS v4.0); 8.6 (CVSS v3.1)
CVSS severityHigh
Exploitation statusCISA states that no known public exploitation specifically targeting these vulnerabilities has been reported to it at publication.; no exploitation claim is inferred.

What Changed

CISA disclosed an integer underflow in libumqtt and states that the repository owners did not respond to coordination. The advisory does not identify a fixed release or authorize a particular downstream patch.

What To Validate Now

  1. Inventory. Review dependency inventories, firmware components and SBOMs for libumqtt, then identify product owners and actual network data paths.
  2. Establish applicability. Confirm the embedded version and whether untrusted traffic can reach the affected library. Do not assume all MQTT implementations use libumqtt.
  3. Remediate. Contact the project or integrating vendor for supported remediation. Apply CISA’s network-exposure and segmentation guidance as appropriate after operational impact analysis.
  4. Validate. Record vendor responses, compensating controls and residual-risk decisions; validate connectivity and availability monitoring without sending malformed traffic to production systems.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

No fixed version is stated. Replacing an embedded library or blocking MQTT traffic can disrupt equipment; require supplier support and controlled testing.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.