# CVE-2026-68967: Out-of-bounds Write in Bendix EC80 Brake ECU

> An attacker can exploit an out-of-bounds write in the Bendix EC80 Brake ECU to crash the system or potentially execute arbitrary code.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA: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:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-4qwq-727c-3x66

## What is CVE-2026-68967?

CVE-2026-68967 is a high-severity memory corruption vulnerability in Bendix EC80ESP 2nd CAN, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Bendix EC80 Brake ECU is vulnerable to an out-of-bounds write, which could allow an attacker 
to deliver a payload that could establish an arbitrary write primitive, 
which could crash the ECU.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-68967 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68967 is a high-severity memory corruption vulnerability in Bendix EC80ESP 2nd CAN, published on 27 Aug 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-68967 in the wild and no public exploit code.

Affected product: Bendix EC80ESP 2nd CAN. 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-68967/ (Markdown: https://insights.sbomify.com/CVE-2026-68967/index.md)
```

## Sources

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

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