Out-of-bounds Read

CWE-125 · 6 records · 4 with a public proof-of-concept

Records the NVD classes as Out-of-bounds Read (CWE-125), highest CVSS first.

  1. CRITICAL 9.8CVE-2026-71256public PoC

    nanoMODBUS through v1.23.0 contains an out-of-bounds stack read leading to a wild-pointer write in nmbs_read_device_identification_basic / recv_read_device_identification_res in nanomodbus.c. A fixed 3-element stack array order[3] = {0,1,2} maps object IDs to

    AI risk analysis on Exploit-DB.ai →

  2. HIGH 7.5CVE-2026-67857public PoC

    open62541 1.5.5 contains an out-of-bounds read in the client-side function responseReadNamespacesArray() in src/client/ua_client_connect.c.

    AI risk analysis on Exploit-DB.ai →

  3. MEDIUM 6.5CVE-2026-70368

    A stack-based out-of-bounds read vulnerability exists in the "s_vlog" function of stunnel, when handling oversized log messages via "vsnprintf". A remote attacker with network access to a stunnel service can send protocol inputs that trigger a log message long

    AI risk analysis on Exploit-DB.ai →

  4. MEDIUM 5.5CVE-2026-68743

    A flaw was found in SSSD. The extract_authtok_v1() function in the PAM responder does not validate the auth_token_length field against the remaining buffer size before processing. A local attacker can exploit this via a crafted protocol v1 request to the PAM r

    AI risk analysis on Exploit-DB.ai →

  5. MEDIUM 5.3CVE-2026-45705public PoC

    OpenSIPS is a Session Initiation Protocol (SIP) server implementation. In versions prior to 3.6.6 and 4.0.0-rc1, the find_line_delimiter() function in the multipart body parser performs an out-of-bounds read via strncmp() when searching for MIME boundary delim

    AI risk analysis on Exploit-DB.ai →

  6. LOW 3.3CVE-2026-18790public PoC

    A weakness has been identified in Systerel S2OPC up to 1.7.3. This affects the function LockedStaMac_ProcessMsg_DeleteMonitoredItemsResponse of the file src/ClientServer/frontend/client_wrapper/internal/state_machine.c of the component DeleteMonitoredItemsRequ

    AI risk analysis on Exploit-DB.ai →