Skip to content

Product

Eclipse Foundation mosquitto vulnerabilities

4 published CVES affecting Eclipse Foundation mosquitto, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
4
Critical
0
High
2
Medium
2
Low
0
Unscored
0
CISA KEV
0

Latest Eclipse Foundation mosquitto CVEs

Newest publication first

  1. CVE-2024-3935 Eclipse Mosquito: Double free vulnerability

    Published
    MediumCVSS 6.0 EPSS 0.75%

    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 PUBLI...

  2. CVE-2024-10525 Eclipse Mosquito: Heap Buffer Overflow in my_subscribe_callback

    Published
    HighCVSS 7.2 EPSS 59.2%

    In Eclipse Mosquitto, from version 1.3.2 through 2.0.18, if a malicious broker sends a crafted SUBACK packet with no reason codes, a client using libmosquitto may make out of bounds memory access when acting in its on_subscribe callback. This affects the mosquitto_sub and mosquit...

  3. CVE-2024-8376 Memory leak

    Published
    HighCVSS 7.2 EPSS 0.75%

    In Eclipse Mosquitto up to version 2.0.18a, an attacker can achieve memory leaking, segmentation fault or heap-use-after-free by sending specific sequences of "CONNECT", "DISCONNECT", "SUBSCRIBE", "UNSUBSCRIBE" and "PUBLISH" packets.

  4. CVE-2017-7650 In Mosquitto before 1.4.12, pattern based ACLs can be bypassed by clients that set their username/client id to '#' or '+'. This allows locally or remotely connected clients to access MQTT topics that....

    Published
    MediumCVSS 6.5 EPSS 2.5%

    In Mosquitto before 1.4.12, pattern based ACLs can be bypassed by clients that set their username/client id to '#' or '+'. This allows locally or remotely connected clients to access MQTT topics that they do have the rights to. The same issue may be present in third party authent...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.