{"id":"CVE-2026-71255","published":"2026-08-05T12:18:57.727","lastModified":"2026-08-10T12:17:28.070","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.","cvssScore":8.6,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H","cwes":["CWE-787"],"vendors":[],"products":[],"references":[{"url":"https://github.com/debevv/nanoMODBUS","tags":[]},{"url":"https://github.com/debevv/nanoMODBUS/blob/master/nanomodbus.c","tags":[]}],"exploitRefs":[{"url":"https://github.com/debevv/nanoMODBUS","tags":[]},{"url":"https://github.com/debevv/nanoMODBUS/blob/master/nanomodbus.c","tags":[]}],"hasPoc":true,"ai":{"summary":"The flaw in nanoMODBUS allows for an out-of-bounds write due to improper validation of the object_length field, which can lead to potential code execution or data corruption.","exploitability":"Exploitation is moderately hard as it requires precise control over the object_length field, but preconditions include the presence of a vulnerable version of nanoMODBUS in the system.","blast_radius":"If exploited, this flaw could result in significant damage, including unauthorized code execution or data corruption on the affected system.","remediation":"Upgrade to nanoMODBUS v1.23.1 or later.","detection":"No reliable host or network indicator is derivable from the published description.","tags":["ics","modbus","buffer-overflow"],"model":"qwen2.5:7b-instruct","analyzedAt":"2026-10-02T08:49:05.970Z"}}