# CVE-2026-37536: Memory corruption in n/a

> A stack buffer overflow in the UDS diagnostic library allows attackers to execute arbitrary code or cause denial of service via crafted diagnostic requests.

- **Severity:** High 8.8 (`CVSS:3.1/AC:L/AV:A/A:H/C:H/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-64w6-xcpc-2gc3

## What is CVE-2026-37536?

CVE-2026-37536 is a high-severity memory corruption 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

miaofng/uds-c commit e506334e270d77b20c0bc259ac6c7d8c9b702b7a (2016-10-05) contains a stack buffer overflow in send_diagnostic_request. A 6-byte stack buffer (MAX_DIAGNOSTIC_PAYLOAD_SIZE=6) receives memcpy at offset 1+pid_length with payload_length bytes. MAX_UDS_REQUEST_PAYLOAD_LENGTH=7, so 1+2+7=10 exceeds buffer by 4 bytes. No bounds check on payload_length before memcpy.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-37536 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-37536 is a high-severity memory corruption 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-37536 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-37536/ (Markdown: https://insights.sbomify.com/CVE-2026-37536/index.md)
```

## Sources

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

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