CVE-2026-51539
Deferred Deferred - Pending Action

Denial of Service in libmodbus Windows Receive Loop

Vulnerability report for CVE-2026-51539, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-14

Assigner: MITRE

Description

A Denial of Service (DoS) vulnerability exists in the receive loop of libmodbus 3.1.12 when running on Windows. The issue stems from improper timeout management during network read operations.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-14
Generated
2026-08-03
AI Q&A
2026-07-14
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
libmodbus libmodbus 3.1.12

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-51539 is a Denial of Service (DoS) vulnerability in libmodbus version 3.1.12 when running on Windows. The vulnerability occurs in the receive loop of the software due to improper timeout management during network read operations. This means that an attacker could exploit this flaw to cause the application to stop responding or crash, leading to a denial of service condition.

Detection Guidance

Detecting this vulnerability on your network or system may require checking for the presence of the affected libmodbus version (3.1.12) running on Windows systems. Since the issue is related to improper timeout management during network read operations, you can look for signs of abnormal behavior in applications using libmodbus, such as unexpected crashes or unresponsiveness during network communication.

To identify systems running libmodbus 3.1.12 on Windows, you can use the following approaches:

  • Check installed software versions on Windows systems where libmodbus is deployed. Use the Windows command line to query installed programs: wmic product get name,version | find "libmodbus"
  • Monitor network traffic for modbus protocol communications. Tools like Wireshark can be used to capture and analyze modbus traffic. Look for unusual patterns or repeated failed connections that may indicate timeout issues.
  • Review application logs for errors related to modbus communication, such as timeouts or connection resets. These may indicate the presence of the vulnerability.

Since the vulnerability is specific to the receive loop in libmodbus, there are no direct commands to detect it, but monitoring for the above signs can help identify potentially vulnerable systems.

Impact Analysis

This vulnerability can impact you in the following ways:

  • If you are using libmodbus 3.1.12 on Windows, an attacker could exploit this vulnerability to cause a denial of service, disrupting the availability of your application or system.
  • The attack can be launched remotely without requiring any privileges or user interaction, making it easier for attackers to exploit.
  • The CVSS base score of 7.5 indicates a high severity, meaning the impact on availability is significant, though it does not affect confidentiality or integrity.
Compliance Impact

This vulnerability may affect compliance with common standards and regulations in the following ways:

  • GDPR: While GDPR primarily focuses on data privacy and protection, a denial of service attack could disrupt services handling personal data, potentially leading to non-compliance if it affects data availability or security measures.
  • HIPAA: For organizations handling protected health information (PHI), a DoS vulnerability could impact the availability of critical systems, which may violate HIPAA requirements for ensuring the confidentiality, integrity, and availability of PHI.
  • Other standards like ISO 27001 or NIST frameworks require maintaining system availability and protecting against disruptions. This vulnerability could lead to non-compliance if not addressed promptly.
Mitigation Strategies

To mitigate this Denial of Service (DoS) vulnerability in libmodbus 3.1.12 on Windows, consider the following immediate steps:

  • Upgrade libmodbus to a patched version if available. Check the official libmodbus repository or vendor updates for a fixed release.
  • If upgrading is not immediately possible, apply network-level protections to limit exposure. Restrict modbus traffic to trusted sources using firewalls or network segmentation.
  • Implement rate limiting or connection throttling for modbus traffic to reduce the risk of exploitation. This can help prevent an attacker from triggering the DoS condition.
  • Monitor systems using libmodbus for signs of exploitation, such as unexpected crashes or high resource usage during modbus communication.
  • Consider temporarily disabling modbus services if they are not critical to operations until a patch or workaround is applied.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-51539. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart