CVE-2026-54410: nanoMODBUS Off-by-One Buffer Overflow in recv_msg_header() via Crafted MBAP Length Field

Published Jun 14, 2026
·
Updated

nanoMODBUS through v1.23.0 contains an off-by-one buffer overflow in the recvmsgheader() function of the Modbus/TCP server that allows remote unauthenticated attackers to write one attacker-controlled byte past the end of the 260-byte receive buffer by sending a crafted MBAP frame whose Length field is set to 255. The overflow corrupts the adjacent buffer-index field of the nanoMODBUS state structure, resulting in denial of service through invalid memory accesses and, on bare-metal and RTOS targets without memory protection, one-byte information disclosure and writes to unintended register addresses on the Write Multiple Registers (FC16) handler path.

Affected Software

1 affected component
nanoMODBUS nanoMODBUS<=1.23.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove nanoMODBUS from your environment.

    Uninstall nanoMODBUS from systems where Modbus/TCP functionality is not required.

  2. Configuration

    Disable the Modbus/TCP server if it is not required to eliminate exposure to crafted MBAP frames that can trigger the off-by-one overflow.

    nanoMODBUS Modbus/TCP server enabled = false
  3. Configuration

    Disable the FC16 (Write Multiple Registers) handler if not required to prevent unintended register writes triggered by the overflow.

    nanoMODBUS Write Multiple Registers (FC16) handler enabled = false
  4. Compensating control

    Restrict network access to the Modbus/TCP interface to trusted hosts only using firewall rules, ACLs, or network segmentation to prevent remote unauthenticated attackers from sending crafted MBAP frames.

  5. Compensating control

    Isolate or place additional network controls around bare-metal and RTOS targets without memory protection to limit exposure, as these targets are at higher risk of information disclosure and unintended writes.

  6. Operational

    Monitor devices for crashes, signs of denial-of-service, and unexpected register writes; take affected devices offline for analysis and recovery if exploitation is suspected.

Event History

Jun 14, 2026
CVE Published
via MITRE·05:10 PM
Data Sourced
via MITRE·05:10 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-54410?

The severity of CVE-2026-54410 is rated high with a score of 8.6.

2

What type of vulnerability is CVE-2026-54410?

CVE-2026-54410 is a buffer overflow vulnerability due to an off-by-one error.

3

How can I mitigate CVE-2026-54410?

Mitigation of CVE-2026-54410 includes updating nanoMODBUS to a version beyond 1.23.0.

4

Is remote authentication required to exploit CVE-2026-54410?

No, CVE-2026-54410 can be exploited by remote unauthenticated attackers.

5

What is the impact of a successful exploit of CVE-2026-54410?

A successful exploit of CVE-2026-54410 allows attackers to write one controlled byte past the end of the receive buffer, potentially leading to arbitrary code execution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203