VulnerabilityPublished 4 Dec 2024Updated 5 Dec 2024

CVE-2024-50947: KMQTT

Affects KMQTTSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubdavidepianca98/KMQTT`pkg:github/davidepianca98/KMQTT`Other threats	Affected =0.2.7	Fixed in–

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

AI-suggested

Restrict network access to kmqtt services by implementing firewall rules and network segmentation to limit exposure to trusted hosts only.
Monitor network traffic for unusual or malformed MQTT requests that could indicate exploitation attempts.
Deploy intrusion detection or prevention systems (IDS/IPS) with signatures or heuristics targeting anomalous MQTT traffic patterns.
Regularly check for and apply vendor or community patches or updates addressing this vulnerability once available.
Consider deploying rate limiting or connection throttling on MQTT brokers or clients to mitigate potential DoS attempts.
Implement robust logging and alerting on kmqtt services to detect crashes or service interruptions promptly.
Evaluate alternative MQTT implementations with better security track records if patching is delayed.
Conduct penetration testing and vulnerability assessments focused on MQTT infrastructure to identify and remediate similar weaknesses.

Description

An issue in kmqtt v0.2.7 allows attackers to cause a Denial of Service (DoS) via a crafted request.

Impact

The primary impact of CVE-2024-50947 is the disruption of availability for systems using kmqtt version 0.2.7. Organizations relying on kmqtt for MQTT messaging, especially in IoT deployments, industrial automation, or real-time data exchange, may experience service outages or degraded performance due to this DoS vulnerability. Such disruptions can lead to operational downtime, loss of telemetry data, delayed command execution, and potential cascading failures in dependent systems. Since the vulnerability does not affect confidentiality or integrity, data theft or manipulation is not a direct concern. However, the availability impact alone can have significant consequences in critical infrastructure, manufacturing, smart city applications, and other environments where MQTT is widely used. The ease of exploitation without authentication or user interaction increases the risk of widespread attacks, particularly if exposed to the internet or untrusted networks.

References

Community reviews

Loading reviews…