Skip to main content
VulnerabilityPublished Updated

CVE-2024-36844: libmodbus · Use After Free

Affects libmodbusSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 May 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubstephane/libmodbuspkg:github/stephane/libmodbusOther threatsAffected
  • =3.1.6
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 vendor communications closely for official patches or updates addressing CVE-2024-36844 and apply them promptly once available.
  2. Until patches are released, implement strict network segmentation to isolate systems running libmodbus unit-test-server components from untrusted networks.
  3. Employ firewall rules or intrusion prevention systems (IPS) to block or restrict Modbus traffic, especially to the unit-test-server ports, from unauthorized sources.
  4. Disable or remove the unit-test-server component in production environments if it is not required, reducing the attack surface.
  5. Conduct thorough asset inventories to identify all instances of libmodbus usage and assess exposure.
  6. Implement continuous monitoring and anomaly detection for unusual Modbus traffic patterns indicative of exploitation attempts.
  7. Educate operational technology (OT) and IT teams about this vulnerability to ensure coordinated response and mitigation efforts.
  8. Consider deploying application-layer gateways or protocol-aware proxies that can validate Modbus messages and filter malformed or suspicious packets.

Description

libmodbus v3.1.6 was discovered to contain a use-after-free via the ctx->backend pointer. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted message sent to the unit-test-server.

References

Community reviews

Loading reviews…