1834 matches found
EUVD-2026-53332
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus client-side recvreaddeviceidentificationres function FC 0x2B/MEI 0x0E, Read Device Identification in nanomodbus.c. The server-supplied objectlength field 0-246 is validated only against the remaining PDU size ressizeleft and...
CVE-2026-71255 nanoMODBUS Client-Side Out-of-Bounds Write via object_length in recv_read_device_identification_res()
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus client-side recvreaddeviceidentificationres function FC 0x2B/MEI 0x0E, Read Device Identification in nanomodbus.c. The server-supplied objectlength field 0-246 is validated only against the remaining PDU size ressizeleft and...
CVE-2026-71255
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus client-side recvreaddeviceidentificationres function FC 0x2B/MEI 0x0E, Read Device Identification in nanomodbus.c. The server-supplied objectlength field 0-246 is validated only against the remaining PDU size ressizeleft and...
EUVD-2026-53331
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handlereadfilerecord function FC 0x14, Read File Record in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request's recordlength is at most 124, but i...
CVE-2026-71254 nanoMODBUS Server-Side Out-of-Bounds Write in handle_read_file_record()
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handlereadfilerecord function FC 0x14, Read File Record in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request's recordlength is at most 124, but i...
CVE-2026-71254
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handlereadfilerecord function FC 0x14, Read File Record in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request's recordlength is at most 124, but i...
CVE-2026-71254: Out-of-bounds Write
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handlereadfilerecord function FC 0x14, Read File Record in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request's recordlength is at most 124, but i...
Debian dla-4714 : libmodbus-dev - security update
The remote Debian 12 host has packages installed that are affected by a vulnerability as referenced in the dla-4714 advisory. - ------------------------------------------------------------------------- Debian LTS Advisory DLA-4714-1 [email protected] https://www.debian.org/lts/security/...
[SECURITY] [DLA 4714-1] libmodbus security update
------------------------------------------------------------------------- Debian LTS Advisory DLA-4714-1 [email protected] https://www.debian.org/lts/security/ Thorsten Alteholz August 01, 2026 https://wiki.debian.org/LTS -...
CVE-2026-44107
A reboot of the charging controller can be triggered via Modbus TCP without authentication. Therefore, when the Modbus functionality is enabled by opening the port that CharxModbusServer is listening, an unauthenticated attacker can perform a Denial-of-Service attack...
CVE-2026-44092
An unauthenticated remote attacker can inject malicious input into the ModbusServer application because it does not validate the input it fetches from MQTT. This may lead to integrity and availability loss...
CVE-2026-44107 Exposed Reboot via Modbus
A reboot of the charging controller can be triggered via Modbus TCP without authentication. Therefore, when the Modbus functionality is enabled by opening the port that CharxModbusServer is listening, an unauthenticated attacker can perform a Denial-of-Service attack...
CVE-2026-44107 Exposed Reboot via Modbus
A reboot of the charging controller can be triggered via Modbus TCP without authentication. Therefore, when the Modbus functionality is enabled by opening the port that CharxModbusServer is listening, an unauthenticated attacker can perform a Denial-of-Service attack...
CVE-2026-44107
A reboot of the charging controller can be triggered via Modbus TCP without authentication. Therefore, when the Modbus functionality is enabled by opening the port that CharxModbusServer is listening, an unauthenticated attacker can perform a Denial-of-Service attack...
EUVD-2026-51042
A reboot of the charging controller can be triggered via Modbus TCP without authentication. Therefore, when the Modbus functionality is enabled by opening the port that CharxModbusServer is listening, an unauthenticated attacker can perform a Denial-of-Service attack...
CVE-2026-44107
CVE-2026-44107 describes an unauthenticated Denial-of-Service vulnerability in the Modbus TCP interface of the CharxModbusServer. If Modbus functionality is enabled by opening the port, an attacker can trigger a reboot of the charging controller via Modbus TCP without authentication, leading to s...
CVE-2026-44092
CVE-2026-44092 affects the ModbusServer application. An unauthenticated remote attacker can inject malicious input because input fetched from MQTT is not validated, leading to integrity and availability loss. Root cause: lack of validation in input handling for MQTT-derived data. Reported metrics...
CVE-2026-44092 Missing input validation / stripping of CRLF characters in SystemConfigManager
An unauthenticated remote attacker can inject malicious input into the ModbusServer application because it does not validate the input it fetches from MQTT. This may lead to integrity and availability loss...
CVE-2026-44092
An unauthenticated remote attacker can inject malicious input into the ModbusServer application because it does not validate the input it fetches from MQTT. This may lead to integrity and availability loss...
CVE-2026-44107: Exposed Dangerous Method or Function
A reboot of the charging controller can be triggered via Modbus TCP without authentication. Therefore, when the Modbus functionality is enabled by opening the port that CharxModbusServer is listening, an unauthenticated attacker can perform a Denial-of-Service attack...