# CVE-2026-73523: COVESA Open1722 0.9.2 Stack Memory Disclosure via acf-can-listener.c Integer Truncation

> Remote attackers can leak stack memory onto the CAN bus via integer truncation in COVESA Open1722, exposing sensitive process data.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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:** 17 Aug 2026
- **Also known as:** GHSA-ggx8-w5hw-4h29

## What is CVE-2026-73523?

CVE-2026-73523 is a high-severity 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 an integer truncation vulnerability in acf-can-listener.c that allows unauthenticated remote attackers to cause the CAN listener to transmit process stack memory onto the CAN bus by sending a rejected UDP datagram with a matching AVTP stream ID. The num_can_msgs variable declared as uint8_t truncates the -1 error return value from avtp_to_can() to 255, causing a write loop to iterate 255 times over a 15-slot stack array and leak approximately 18 KB of adjacent stack memory as roughly 240 CAN frames to any recipient on the CAN bus.

Weakness: CWE-197 (Numeric Truncation Error)

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


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

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

## Is CVE-2026-73523 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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