{"id":"CVE-2026-37535","aliases":["EUVD-2026-26688","GHSA-v288-v38p-24mh"],"status":"published","title":"openxc/isotp-c thru commit 5a5d19245f65189202719321facd49ce6f5d46ac (2021-08-09) contains an out...","description":"openxc/isotp-c thru commit 5a5d19245f65189202719321facd49ce6f5d46ac (2021-08-09) contains an out-of-bounds read in the ISO-TP Single Frame receive handler, where the 4-bit payload length nibble is used directly as the memcpy size without validating it against the actual CAN data length. A malicious CAN frame with an oversized length nibble can cause memory reads beyond the buffer, allowing attackers to cause a denial of service, or gain sensitive information.","severity":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AC:L/AV:A/A:H/C:L/I:N/PR:N/S:U/UI:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00205,"percentile":0.10596,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-125"],"published":"2026-05-01T00:00:00Z","modified":"2026-06-17T10:41:34Z","references":[{"url":"https://github.com/openxc/isotp-c"},{"url":"https://github.com/openxc/isotp-c/blob/master/src/isotp/receive.c"},{"url":"https://gist.github.com/sgInnora/f4ac66faeefe07a653ceeb3f58cdc381"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-37535"},{"url":"https://github.com/advisories/GHSA-v288-v38p-24mh"}],"sources":{"cve":[{"id":"CVE-2026-37535","description":"openxc/isotp-c thru commit 5a5d19245f65189202719321facd49ce6f5d46ac (2021-08-09) contains an out-of-bounds read in the ISO-TP Single Frame receive handler, where the 4-bit payload length nibble is used directly as the memcpy size without validating it against the actual CAN data length. A malicious CAN frame with an oversized length nibble can cause memory reads beyond the buffer, allowing attackers to cause a denial of service, or gain sensitive information.","status":"published","published":"2026-05-01T00:00:00Z","modified":"2026-05-01T19:45:11.301Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AC:L/AV:A/A:H/C:L/I:N/PR:N/S:U/UI:N","level":"high","assessor":"cna"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T13:39:16.730222Z"}],"euvd":[{"id":"EUVD-2026-26688","description":"openxc/isotp-c thru commit 5a5d19245f65189202719321facd49ce6f5d46ac (2021-08-09) contains an out-of-bounds read in the ISO-TP Single Frame receive handler, where the 4-bit payload length nibble is used directly as the memcpy size without validating it against the actual CAN data length. A malicious CAN frame with an oversized length nibble can cause memory reads beyond the buffer, allowing attackers to cause a denial of service, or gain sensitive information.","status":"published","published":"2026-05-01T00:00:00Z","modified":"2026-05-01T19:45:11Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AC:L/AV:A/A:H/C:L/I:N/PR:N/S:U/UI:N","level":"high"}],"updated_at":"2026-11-02T19:05:18.340967Z"}],"ghsa":[{"id":"GHSA-v288-v38p-24mh","title":"openxc/isotp-c thru commit 5a5d19245f65189202719321facd49ce6f5d46ac (2021-08-09) contains an out...","description":"openxc/isotp-c thru commit 5a5d19245f65189202719321facd49ce6f5d46ac (2021-08-09) contains an out-of-bounds read in the ISO-TP Single Frame receive handler, where the 4-bit payload length nibble is used directly as the memcpy size without validating it against the actual CAN data length. A malicious CAN frame with an oversized length nibble can cause memory reads beyond the buffer, allowing attackers to cause a denial of service, or gain sensitive information.","status":"published","published":"2026-05-01T18:31:24Z","modified":"2026-05-01T21:31:20Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","level":"high"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T15:07:52.84276Z"}],"nvd":[{"id":"CVE-2026-37535","description":"openxc/isotp-c thru commit 5a5d19245f65189202719321facd49ce6f5d46ac (2021-08-09) contains an out-of-bounds read in the ISO-TP Single Frame receive handler, where the 4-bit payload length nibble is used directly as the memcpy size without validating it against the actual CAN data length. A malicious CAN frame with an oversized length nibble can cause memory reads beyond the buffer, allowing attackers to cause a denial of service, or gain sensitive information.","status":"published","published":"2026-05-01T17:16:23.21Z","modified":"2026-06-17T10:41:34.46Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","level":"high","assessor":"secondary"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:12:17.022502Z"}]}}
