Skip to main content
CVE-2024-3935VulnerabilityPublished Updated

CVE-2024-3935: Eclipse Foundation mosquitto · Double Free

Affects Eclipse Foundation mosquittoSource CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubeclipse-mosquitto/mosquittopkg:github/eclipse-mosquitto/mosquittoOther threatsAffected
  • =2.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor for updates from the Eclipse Foundation and apply patches or upgrades to Mosquitto versions beyond 2.0.18 as soon as they become available. 2. Temporarily disable or restrict outgoing bridge connections that use topic remapping until patched. 3. Implement strict access controls and authentication mechanisms to limit which clients can establish bridge connections or publish to sensitive topics. 4. Use network segmentation to isolate MQTT brokers from untrusted networks and reduce exposure to potentially malicious clients. 5. Deploy MQTT traffic anomaly detection to identify unusual PUBLISH packets or patterns indicative of exploitation attempts. 6. Regularly audit broker configurations to ensure topic remapping is only used where necessary and securely configured. 7. Consider fallback or redundancy mechanisms for MQTT brokers to maintain service availability during potential crashes. 8. Educate operational teams about the vulnerability and signs of broker instability to enable rapid response.

Description

In Eclipse Mosquito, versions from 2.0.0 through 2.0.18, if a Mosquitto broker is configured to create an outgoing bridge connection, and that bridge connection has an incoming topic configured that makes use of topic remapping, then if the remote connection sends a crafted PUBLISH packet to the broker a double free will occur with a subsequent crash of the broker.

References

Community reviews

Loading reviews…