aMQTT denial of service in subscription filter matching
Only affects amqtt 0.11.0 through 0.11.3, the MQTT broker library by Yakifo. Fixed in 0.11.4. No vendor severity rating is given beyond the CVSS score of 8.7 (high).
- Exploited
- No known exploitation
- Fix
- Fixed in 0.11.4
- Who is exposed
- Default setups
Summary
Anonymous attackers over the network can send a crafted subscription filter followed by a publish to make the aMQTT broker's event loop hang, stopping message delivery and new connections until the broker is restarted. Authenticated clients allowed to create subscriptions and publish can also trigger it when authentication is enabled.
Written by a model
Original description
aMQTT is an open source MQTT broker and client. From 0.11.0 until 0.11.4, add_subscription() in amqtt/broker.py accepts malformed single-level + wildcard placement because it checks substrings instead of validating each slash-delimited level. The _matches() function converts each + into a greedy regular-expression fragment and evaluates it with re.fullmatch(), allowing a filter containing many adjacent + characters to trigger catastrophic backtracking when compared with a topic that partially matches but ultimately fails. Because matching runs synchronously in _run_broadcast(), one subscription followed by a publish can block the broker event loop, stopping message delivery and new connection processing until restart. Anonymous clients can trigger the issue with the default configuration. Any authenticated client permitted to create arbitrary subscriptions and publish messages may still exploit it when authentication is enabled. This issue is fixed in version 0.11.4.
Who should check
Teams running the amqtt MQTT broker from 0.11.0 through 0.11.3, where anonymous or authenticated clients can create subscriptions.
Not fixed by: Authentication alone is not a sufficient mitigation.
“Affected versions: >= 0.11.0, <= 0.11.3”
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 0.11.4.
Workaround: Install a topic-filtering plugin that rejects malformed wildcard subscriptions before they are added to the broker.
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-104199 (aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation), 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-104199 (entry last updated 2026-11-19):
Affected:
- Yakifo amqtt: from 0.11.0, fixed in 0.11.4
Fixed versions: 0.11.4.
Conditions (all must be true for the bug to be hit):
- Affected amqtt versions are 0.11.0 through 0.11.3. (source: https://github.com/Yakifo/amqtt/security/advisories/GHSA-2hjf-7455-w946)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
Workaround: Install a topic-filtering plugin that rejects malformed wildcard subscriptions before they are added to the broker. (source: https://github.com/Yakifo/amqtt/security/advisories/GHSA-2hjf-7455-w946)
CISA KEV: CVE-2026-104199 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104199 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/Yakifo/amqtt/security/advisories/GHSA-2hjf-7455-w946
- https://github.com/Yakifo/amqtt/pull/361
- https://github.com/Yakifo/amqtt/commit/e48a8a65027667f936d415db7f01d3ac350104e0
- https://github.com/Yakifo/amqtt/releases/tag/v0.11.4
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-104199
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-104199"}.Affected versions
- Yakifo amqttFrom 0.11.0 · fixed in 0.11.4
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Yakifo/amqtt · Advisory GHSA-2hjf-7455-w946 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-104199 |
| Record | NVD · CVE-2026-104199 |
| Other links 3 | |
| Repository | GitHub · Yakifo/amqtt · Pull request #361 |
| Repository | GitHub · Yakifo/amqtt · Commit e48a8a65 |
| Repository | GitHub · Yakifo/amqtt · Release v0.11.4 |
Questions about CVE-2026-104199
Is CVE-2026-104199 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?
A single client can send one specially crafted SUBSCRIBE packet followed by one PUBLISH packet and freeze the entire broker. Message delivery, new connections, keepalive and broadcast processing stop until the process is restarted.
Source: github.com
Which versions are affected by CVE-2026-104199?
amqtt: from 0.11.0 before 0.11.4.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 0.11.0 through 0.11.3 of amqtt are affected. To check a installation, look at the installed amqtt version, for example with pip show amqtt.
Source: github.com
How do I fix CVE-2026-104199?
Upgrade amqtt to version 0.11.4, which the vendor says contains the patch and which all users should install.
Source: github.com
Related
- CVE-2026-130176aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes
- CVE-2026-77367Daptin: Unauthenticated SQL Injection via the `sort` query parameter on every entity list endpoint
- CVE-2026-131199SPL Injection through the Risk Event Timeline REST API in Splunk Enterprise Security
- CVE-2026-93914Dimension Improper Input Validation in Database Snapshot Restore Allows Root Code Execution
- CVE-2026-131210SPL Injection through Finding Exclusion Rules in Splunk Enterprise Security
- CVE-2026-63202netty-incubator-codec-ohttp BinaryHttpParser: Unauthenticated CPU-exhaustion DoS via infinite loop in field-section decoding
No corrections so far. Something wrong on this page? Report an error.