# CVE-2026-73522: COVESA Open1722 0.9.2 Stack Buffer Overflow via avtp_to_can() in acf-can-listener

> Remote attackers can achieve arbitrary code execution or denial of service via stack buffer overflow in the Open1722 library by sending crafted UDP datagrams.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-r2g8-gx6q-pvxr

## What is CVE-2026-73522?

CVE-2026-73522 is a high-severity memory corruption vulnerability in COVESA Open1722, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

COVESA Open1722 through 0.9.2 contains a stack buffer overflow vulnerability that allows unauthenticated remote attackers to write past the end of a fixed 15-slot stack array by sending a crafted UDP datagram containing more than 15 ACF-CAN messages. The avtp_to_can() function increments its write index without bounding it against the caller-supplied array size, and because the listener accepts datagrams from any sender matching a hardcoded unauthenticated stream ID transmitted in plaintext, attackers can corrupt adjacent stack memory to achieve arbitrary code execution or denial of service.

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

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


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

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

## Is CVE-2026-73522 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-73522 is a high-severity memory corruption vulnerability in COVESA Open1722, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73522 in the wild and no public exploit code.

Affected product: COVESA Open1722. 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-73522/ (Markdown: https://insights.sbomify.com/CVE-2026-73522/index.md)
```

## Sources

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

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