Description
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus client-side recv_read_device_identification_res function (FC 0x2B/MEI 0x0E, Read Device Identification) in nanomodbus.c. The server-supplied object_length field (0-246) is validated only against the remaining PDU size (res_size_left) and is never validated against the caller-supplied buffers_length parameter.
Published: 2026-08-05
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vuln is an out‑of‑bounds write in the nanoMODBUS client routine that processes Read Device Identification responses. A server can supply an object_length value that is not checked against the caller‑supplied buffer length; this allows the function to write past the end of its local buffer, corrupting adjacent memory. Such corruption can compromise data integrity, lead to undefined behavior, and potentially crash the client.

Affected Systems

The issue affects the nanoMODBUS library from debevv. All releases up to v1.23.0 include the flaw. Users must verify the installed package version and seek an updated release from the vendor.

Risk and Exploitability

The CVSS score of 8.6 indicates a high severity. The EPSS score is less than 1 %, suggesting a low probability of exploitation at present, and the vulnerability is not listed in the CISA KEV catalog. The most likely attack vector involves a malicious or compromised Modbus server that responds with a crafted packet containing an overly large object_length field. The client must only accept responses from trusted servers or enforce additional validation to reduce risk.

Generated by OpenCVE AI on August 10, 2026 at 22:17 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the nanoMODBUS library to the latest release that addresses the out‑of‑bounds write.
  • Implement local validation to ensure the server‑supplied object_length does not exceed the actual buffer length before processing the response data.
  • Limit client connections to authenticated or approved Modbus servers, using network controls or firewall rules to mitigate exposure to malicious responses.

Generated by OpenCVE AI on August 10, 2026 at 22:17 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 12:00:00 +0000

Type Values Removed Values Added
Description nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus client-side recv_read_device_identification_res() function (FC 0x2B/MEI 0x0E, Read Device Identification) in nanomodbus.c. The server-supplied object_length field (0-246) is validated only against the remaining PDU size (res_size_left) and is never validated against the caller-supplied buffers_length parameter. After copying data with strncpy(buffers_out[buf_index], str, buffers_length), the code unconditionally writes a NUL terminator at buffers_out[buf_index][object_length]. When a malicious or compromised Modbus server sends a response with object_length greater than or equal to the client's buffers_length, this NUL write lands past the end of the caller-provided buffer, corrupting adjacent stack or heap memory on the client. nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus client-side recv_read_device_identification_res function (FC 0x2B/MEI 0x0E, Read Device Identification) in nanomodbus.c. The server-supplied object_length field (0-246) is validated only against the remaining PDU size (res_size_left) and is never validated against the caller-supplied buffers_length parameter.
Title nanoMODBUS - Client-Side Out-of-Bounds Write via object_length in recv_read_device_identification_res() nanoMODBUS Client-Side Out-of-Bounds Write via object_length in recv_read_device_identification_res()

Mon, 10 Aug 2026 11:45:00 +0000

Type Values Removed Values Added
Title nanoMODBUS Client-Side Out-of-Bounds Write via object_length in recv_read_device_identification_res() nanoMODBUS - Client-Side Out-of-Bounds Write via object_length in recv_read_device_identification_res()

Wed, 05 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
First Time appeared Debevv
Debevv nanomodbus
Vendors & Products Debevv
Debevv nanomodbus

Wed, 05 Aug 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 05 Aug 2026 13:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H'}

cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H'}


Wed, 05 Aug 2026 12:00:00 +0000

Type Values Removed Values Added
Description nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus client-side recv_read_device_identification_res() function (FC 0x2B/MEI 0x0E, Read Device Identification) in nanomodbus.c. The server-supplied object_length field (0-246) is validated only against the remaining PDU size (res_size_left) and is never validated against the caller-supplied buffers_length parameter. After copying data with strncpy(buffers_out[buf_index], str, buffers_length), the code unconditionally writes a NUL terminator at buffers_out[buf_index][object_length]. When a malicious or compromised Modbus server sends a response with object_length greater than or equal to the client's buffers_length, this NUL write lands past the end of the caller-provided buffer, corrupting adjacent stack or heap memory on the client.
Title nanoMODBUS Client-Side Out-of-Bounds Write via object_length in recv_read_device_identification_res()
Weaknesses CWE-787
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H'}


Subscriptions

Debevv Nanomodbus
cve-icon MITRE

Status: PUBLISHED

Assigner: TuranSec

Published:

Updated: 2026-08-10T11:46:16.030Z

Reserved: 2026-08-05T11:43:52.778Z

Link: CVE-2026-71255

cve-icon Vulnrichment

Updated: 2026-08-05T12:29:02.812Z

cve-icon NVD

Status : Deferred

Published: 2026-08-05T12:18:57.727

Modified: 2026-08-26T17:13:24.800

Link: CVE-2026-71255

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T22:30:06Z

Weaknesses