# CVE-2026-37535: Information disclosure in n/a

> An out-of-bounds read in the ISO-TP library allows attackers to disclose sensitive memory or cause denial of service via malicious CAN frames.

- **Severity:** High 7.1 (`CVSS:3.1/AC:L/AV:A/A:H/C:L/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-v288-v38p-24mh

## What is CVE-2026-37535?

CVE-2026-37535 is a high-severity vulnerability in n/a, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-37535?


## How do I fix CVE-2026-37535?

No fix has been published for CVE-2026-37535 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-37535 being exploited?

There is no known exploitation of CVE-2026-37535 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-37535 and fix it if it is affected.

What it is: CVE-2026-37535 is a high-severity vulnerability in n/a, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37535 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-37535/ (Markdown: https://insights.sbomify.com/CVE-2026-37535/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-37535
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-37535
- OSV: https://osv.dev/vulnerability/CVE-2026-37535

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-37535/
Summaries are generated and may contain mistakes; the official description above is the record.