libumqtt memory corruption in MQTT packet parsing
libumqtt 1.1.1 and earlier are affected. CVSS rates it 8.6 (high), and no fixed version is listed.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
libumqtt contains an integer underflow flaw that a remote attacker can trigger over the network without logging in. Successful exploitation could cause a denial of service, memory corruption, or information disclosure.
Written by a model
Original description
libumqtt is vulnerable to an integer underflow which may allow a remote attacker to cause a denial of service, memory corruption, or information disclosure.
Who should check
Teams running libumqtt 1.1.1 or earlier, the MQTT client C library based on libev, including Lua-binding users
“libumqtt <=1.1.1 (CVE-2026-125132)”
What to do
Workaround: The checked facts name no workaround. Until a fix is available, limit exposure to untrusted remote input where libumqtt is used, based on your own assessment.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125132 (libumqtt Integer Underflow), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-125132 (entry last updated 2026-11-20):
Affected:
- libumqtt libumqtt: through 1.1.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- libumqtt version 1.1.1 or earlier is affected (source: https://www.cisa.gov/news-events/ics-advisories/icsa-26-323-03)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-125132 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125132 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/zhaojh329/libumqtt
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-323-03
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-323-03.json
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-125132
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125132"}.Affected versions
- libumqtt libumqttthrough 1.1.1
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch5/5No patch listed yet
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
- Would score about 39 if advisories confirm default setups are exposed
Timeline
- cve.now early warning
CISA warns of integer underflow flaw in libumqtt 1.1.1 and earlier, with no fix available
1 day - CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-125132 |
| Record | NVD · CVE-2026-125132 |
| Other links 3 | |
| Repository | GitHub · zhaojh329/libumqtt · Repository |
| Repository | GitHub · cisagov/CSAF · csaf_files/OT/white/2026/icsa-26-323-03.json |
| Link | cisa.gov · news-events/ics-advisories/icsa-26-323-03 |
Questions about CVE-2026-125132
Is CVE-2026-125132 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The flaw is an integer underflow that may let a remote attacker cause a denial of service, memory corruption, or information disclosure.
Source: cisa.gov
Which versions are affected by CVE-2026-125132?
libumqtt: through 1.1.1.
Source: cve.now feed data
Am I affected, and how do I check?
libumqtt version 1.1.1 and earlier are affected, per the product range starting at 0 through 1.1.1. Check the libumqtt version in use against that range.
Source: cisa.gov
How do I fix CVE-2026-125132?
The checked facts list no fixed version or vendor patch, so no upgrade target can be given from them. Check the libumqtt project for a newer release.
Source: cisa.gov
What if there's no patch?
The checked facts name no workaround. Until a fix is available, limit exposure to untrusted remote input where libumqtt is used, based on your own assessment.
Source: cisa.gov
Related
- SZB-bf2611689aStarted as this early warning
- CVE-2026-110486Remote heap out-of-bounds read/write in Eclipse Mosquitto
- CVE-2026-129113JSON::XS versions from 4.0_00 before 4.05 for Perl corrupt the incremental buffer length by chopping past its end in incr_skip after a…
- CVE-2026-126979Philips Hue Bridge HomeKit Accessory Protocol chacha20_decrypt Integer Underflow Remote Code Execution Vulnerability
- CVE-2026-123007NGINX ngx_http_v2_module vulnerability
- CVE-2026-107519Dell PowerStore contains an integer underflow vulnerability.
No corrections so far. Something wrong on this page? Report an error.