NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍 PyPI
Not in CISA KEV

CVE-2026-104199 — amqtt

Fix: Yakifo/amqtt@e48a8a6

CVE-2026-104199 is a Improper Input Validation vulnerability in amqtt. A fix is available for amqtt — see the affected versions and patch details below.

aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation

Also known asGHSA-2hjf-7455-w946
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected
🐍amqtt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

amqtt is vulnerable to a remote denial of service caused by improper MQTT topic-filter validation combined with catastrophic regular-expression backtracking.

A single client can freeze the entire broker by sending one specially crafted SUBSCRIBE packet followed by one PUBLISH packet.

The vulnerability is caused by two defects:

  1. add_subscription() validates the placement of the single-level wildcard + using substring checks for /+ and +/, rather than verifying that each /-delimited level containing + is exactly +. This allows malformed filters such as "+/" + "+" * 60 to be accepted instead of rejected with return code 0x80, as required by MQTT-4.7.1-3.
  2. _matches() converts every + character into the greedy regular-expression fragment [^/]* and evaluates the resulting expression with re.fullmatch(). A filter containing many adjacent + characters can cause catastrophic backtracking when matched against a topic that partially matches but ultimately fails.

Topic matching runs synchronously inside the broker’s global broadcast loop. When the malicious match is evaluated, it blocks the asyncio event loop and prevents the broker from processing any other work.

The issue was reproduced using a single raw MQTT 3.1.1 TCP connection with no third-party client dependencies.

Successful exploitation causes:

  • Existing message delivery to stop
  • New MQTT connections to receive no CONNACK
  • Keepalive processing to stop
  • Broadcast processing to stop
  • The broker to remain unavailable until the process is restarted

Under the default configuration, anonymous clients can exploit the vulnerability without credentials. When authentication is enabled, any authenticated client permitted to create arbitrary subscriptions and publish messages may still exploit it. Authentication alone is therefore not a sufficient mitigation.

  • Ecosystem: pip
  • Package: amqtt
  • Affected versions: >= 0.11.0, <= 0.11.3

The vulnerable code is present in the v0.11.0 release commit, 352678c87e50e501a8a5bb91fab73c9400fa046c, and remained present on the main branch as of eeb1e254da9a1e8d9cc68ae754fcedac652e8fc0. Versions before 0.11.0 were not evaluated.

This is a denial-of-service vulnerability only. re.escape() prevents arbitrary regular-expression injection, and there is no known path to remote code execution.

No confidentiality or integrity impact has been identified. Successful exploitation causes a complete loss of availability for the affected broker process.

Patches

The issue has been patched in the v0.11.4 released version; all users should upgrade.

The completed fix:

  • Validate topic filters one level at a time
  • Require any level containing + to be exactly +
  • As part of comprehensive MQTT topic-filter validation, require # to occupy an entire level and appear only as the final level
  • Replace the regular-expression matcher with deterministic, level-by-level MQTT topic matching

Simply changing the validation logic is not sufficient defense in depth if malformed filters can reach the existing regular-expression matcher through another code path.

Workarounds

This is the temporary mitigation that was recommended prior to the patched release: administrators can install a topic-filtering plugin that rejects malformed wildcard subscriptions before they are added to the broker. Place the plugin in an importable Python module, enable it in the broker configuration, and restart the broker.

from amqtt.contexts import Action
from amqtt.plugins.base import BaseTopicPlugin
from amqtt.session import Session

class RejectInvalidTopicFilters(BaseTopicPlugin):
    """A plugin to prevent invalid wildcard subscriptions."""
    async def topic_filtering(
        self, *, session: Session | None = None,
        topic: str | None = None,
        action: Action | None = None
    ) -> bool | None:

        if topic and action == Action.SUBSCRIBE:
            levels = topic.split("/")
            return all(
                level in {"+", "#"} or ("+" not in level and "#" not in level)
                for level in levels
            ) and "#" not in levels[:-1]
        return True
        
config = {
    ...
    'plugins':{
        ...
        'myplugins.RejectInvalidTopicFilters': {}
    }
}

This workaround applies when subscription requests pass through the plugin. If the broker is configured to use a persistent session plugin, restarting the broker alone is not sufficient; any persisted sessions containing malformed topic filters need to be removed.

Restarting the broker restores availability after exploitation, but the broker remains vulnerable until the patch or workaround is installed.

Acknowledgments

aMQTT thanks the following security researchers for their professional, coordinated private disclosure:

  • Yongkang Xiao (Wuhan University)
  • Min Shi (Wuhan University)
  • Qiyi Deng (Wuhan University)
  • Jing Chen (Wuhan University)

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIamqtt≥ 0.11.0&&< 0.11.40.11.4pip install --upgrade 'amqtt==0.11.4'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for amqtt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update amqtt to 0.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-104199 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact `amqtt` is vulnerable to a remote denial of service caused by improper MQTT topic-filter validation combined with catastrophic regular-expression backtracking. A single client can freeze the entire broker by sending one specially crafted `SUBSCRIBE` packet followed by one `PUBLISH` packet. The vulnerability is caused by two defects: 1. `add_subscription()` validates the placement of the single-level wildcard `+` using substring checks for `/+` and `+/`, rather than verifying that each `/`-delimited level containing `+` is exactly `+`. This allows malformed filters such as `"+/"
O3 Security · Impact-Aware SCA

Is CVE-2026-104199 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2026-104199: amqtt RCE — Fixed in 0.11.4