# CVE-2026-37537: Integer overflow in n/a

> An integer underflow in the Open-SAE-J1939 library allows out-of-bounds writes via crafted CAN frames, potentially leading to code execution or crashes.

- **Severity:** High 8.1 (`CVSS:3.1/AC:L/AV:A/A:H/C:N/I:H/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-r65j-732m-pxwm

## What is CVE-2026-37537?

CVE-2026-37537 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

collin80/Open-SAE-J1939 thru commit 744024d4306bc387857dfce439558336806acb06 (2023-03-08) contains an integer underflow leading to out-of-bounds write in Transport Protocol Data Transfer handling. At line 23: uint8_t index = data[0] - 1. When data[0] (sequence number from CAN frame) is 0, index underflows to 255. Subsequent write at tp_dt->data[255*7 + i-1] reaches offset 1791, exceeding the MAX_TP_DT buffer (1785 bytes) by 6 bytes.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-37537 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-37537 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-37537 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-37537/ (Markdown: https://insights.sbomify.com/CVE-2026-37537/index.md)
```

## Sources

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

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