CVE-2026-126763

Description

A flaw was found in Eclipse Mosquitto. A remote MQTT client can cause all pending delayed will messages across the broker to be suppressed by connecting with a will-delay interval and then disconnecting with a shorter interval. In the MQTT (Message Queuing Telemetry Transport) protocol, will messages are automated notifications delivered to subscribers when a client goes offline unexpectedly. By suppressing these notifications, an attacker can prevent monitoring systems and connected services from detecting client failures or disconnections.

Statement

This vulnerability is rated as Moderate impact because an attacker can disrupt delayed MQTT status notifications across the broker without causing a service crash, gaining unauthorized privileges, or compromising confidential message content. In Red Hat environments deploying Mosquitto, the defect affects broker sessions utilizing MQTT v5.0 features when clients negotiate specific will-delay intervals. Because core messaging and broker availability remain functional, and the issue is restricted to the omission of deferred disconnect alerts, the overall operational risk remains bounded.

Mitigation

Restrict broker access to trusted networks using firewall rules and enforce authentication to prevent unauthorized clients from initiating MQTT v5.0 sessions.

1. Restrict the default MQTT port (1883/tcp) to trusted client subnets using firewalld:

firewall-cmd --zone=public --remove-port=1883/tcp --permanent
firewall-cmd --zone=trusted --add-source=<TRUSTED_IP_OR_SUBNET> --permanent
firewall-cmd --reload

2. Require authentication in `/etc/mosquitto/mosquitto.conf` to prevent untrusted anonymous clients from connecting:

allow_anonymous false
password_file /etc/mosquitto/passwd

3. Apply the configuration change:

systemctl reload mosquitto

Caveats: Network filtering and client authentication mitigate unauthorized external exploitation, but authorized clients within trusted networks using MQTT v5.0 can still trigger the issue.

Warning: Modifying firewall configurations or reloading the Mosquitto service may briefly disconnect active client connections.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.3N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactLowN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Understanding the Weakness (CWE)

Other,Integrity,Availability

Technical Impact: Varies by Context; DoS: Resource Consumption (CPU); Modify Memory; Read Memory

When the quantity is not properly validated, then attackers can specify malicious quantities to cause excessive resource allocation, trigger unexpected failures, enable buffer overflows, etc.

Frequently Asked Questions

Want to get errata notifications? Sign up here.