CISA flags libumqtt underflow, vendor offers no fix
The repository owner didn't answer CISA's coordination request, so firewalls and VPNs are the entire mitigation listed.
TL;DR
CISA's advisory for CVE-2026-125132 covers an integer underflow in libumqtt, all versions through 1.1.1. The flaw (CWE-191) scores 8.6 on CVSS v3.1 and lets a remote attacker cause denial of service, memory corruption, or information disclosure across critical manufacturing, energy, information technology, transportation, and water systems deployed worldwide. The remediation field reads "None available"; the repository owner didn't respond to CISA's coordination request, and the advisory lists no vendor patch. No public exploitation has been reported.
CISA's advisory for CVE-2026-125132 covers an integer underflow in libumqtt, all versions through 1.1.1. The flaw (CWE-191) lets a remote attacker cause denial of service, memory corruption, or information disclosure, and it carries a CVSS v3.1 base score of 8.6. CISA lists the affected sectors as critical manufacturing, energy, information technology, transportation, and water and wastewater, deployed worldwide.
What sets this advisory apart is the remediation field. CISA marks it "None available" and notes that the repository owners didn't respond to its coordination request. That means the mitigation section carries no vendor patch, only the standard defensive practices: keep control systems off the internet, place them behind firewalls and isolate them from business networks, and route any remote access through a current VPN.
CISA reports no known public exploitation targeting this vulnerability at this time. But "no patch" plus an unanswered coordination request is a sharper signal than the usual advisory. A vulnerability in a library used by the listed critical-infrastructure sectors normally closes with an update-and-repair; here there's no update to apply, so the defense work stays on the network side until the vendor responds or someone else ships a fix.
Published ·Deep Fathom