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.
CVE-2026-73523
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (2)
Auto-updated Aug 17, 2026COVESA Open1722 0.9.2 Stack Memory Disclosure via acf-can-listener.c Integer Truncation | Advisories | VulnCheck
https://www.vulncheck.com/advisories/covesa-open1722-stack-memory-disclosure-via-acf-can-listener-c-integer-truncationacf-can-listener: stack buffer overflow and stack memory disclosure from one UDP datagram (CVE-2026-73522, CVE-2026-73523) · Issue #154 · COVESA/Open1722 · GitHub
https://github.com/COVESA/Open1722/issues/154Vendor Advisories for CVE-2026-73523(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 00:52 UTCEG score recompute
- 2026-08-21 00:52 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 12:04 UTCGHSA enrichment
- 2026-08-19 23:14 UTCEG score recompute
- 2026-08-19 23:14 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 10:25 UTCGHSA enrichment
- 2026-08-18 21:36 UTCEG score recompute
- 2026-08-18 21:36 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 08:18 UTCGHSA enrichment
- 2026-08-17 19:27 UTCEG score recompute
- 2026-08-17 19:27 UTCGHSA enrichment
- 2026-08-17 18:22 UTCEG score recompute
- 2026-08-17 18:10 UTCEG score recompute
- 2026-08-17 18:09 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-73523?
When was CVE-2026-73523 disclosed?
Is CVE-2026-73523 actively exploited?
What is the CVSS score of CVE-2026-73523?
How do I remediate CVE-2026-73523?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-73523
Is Your Infrastructure Affected by CVE-2026-73523?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.