Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-85724 critical CVSS 9.6

Vulnerability in io.moquette:moquette-broker (CVE-2026-85724)

Summary

Vulnerability in io.moquette:moquette-broker (CVE-2026-85724). Confidential information can be exposed externally. Exploitable via da7f719a6bab9829d520b5838e13ea7b1f9be3ef. Mitigation: upgrade to 0.18.1 or later.

Original description

The description as published by the source.

moquette is reachable by untrusted MQTT clients (anonymous by default), so every byte from any client, including pre-authentication, is untrusted. This is a memory-safe JVM: the ceiling is authorization/ACL bypass + denial of service + cross-session integrity, not RCE (I did not find one and do not claim one). Audited at commit da7f719a6bab9829d520b5838e13ea7b1f9be3ef, module broker/.

What a connecting client can do

  1. (Critical) Bypass pattern-based ACLs across tenants. In AuthorizationsCollector.canDoOperation (AuthorizationsCollector.java:116-131, esp. line 123) the clientId/username is substituted raw into a pattern ACL rule and then wildcard-matched, and the clientId is never validated for MQTT wildcard characters +/# at CONNECT (MQTTConnection.processConnect):

Topic substitutedTopic = new Topic(auth.topic.toString().replace("%c", client).replace("%u", username));
if (topic.match(substitutedTopic)) return true;

A client that connects with clientId + turns sensor/%c/# into the filter sensor/+/#, gaining cross-tenant read AND write. (Precondition: pattern ACL rules configured — a common multi-tenant setup.)

  1. (High) Crash the whole broker. SessionEventLoop (SessionEventLoop.java:40-54) catches only InterruptedException and is never restarted (SessionEventLoopGroup), so any uncaught exception on it wedges every co-located client. Trivially reachable inputs: malformed $share/grp SUBSCRIBE (SharedSubscriptionUtils.extractShareName -> StringIndexOutOfBound…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-85724 has been found in io.moquette:moquette-broker.
Attackers can target a specific entry point like da7f719a6bab9829d520b5838e13ea7b1f9be3ef over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.6/10.
What to do: upgrade io.moquette:moquette-broker to 0.18.1 or later.
If unsure, ask your IT team or search "io.moquette:moquette-broker CVE-2026-85724" on the vendor's site.

CVE-2026-85724 (io.moquette:moquette-broker) — CWE-155 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: da7f719a6bab9829d520b5838e13ea7b1f9be3ef / pattern / AuthorizationsCollector.canDoOperation
Patched: 0.18.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-155) exists in io.moquette:moquette-broker. Attackers reach the vulnerable code path via da7f719a6bab9829d520b5838e13ea7b1f9be3ef.

📍 Affected scope

Check the vendor advisory for the affected versions of io.moquette:moquette-broker. Attack surface: da7f719a6bab9829d520b5838e13ea7b1f9be3ef / pattern / AuthorizationsCollector.canDoOperation.

🔥 Severity

Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.18.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.moquette:moquette-broker を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade io.moquette:moquette-broker to 0.18.1

    ステージング環境で 0.18.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven io.moquette:moquette-broker
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.18.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details