Skip to content
IoT

CVE-2026-73523

HIGH
High
EPSS 0.32%Aug 18, 2026

Integer truncation in Open1722 causes CAN bus stack memory leak.

common questions

Is CVE-2026-73523 being exploited?

Not confirmed. CVE-2026-73523 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.

How severe is CVE-2026-73523?

CVE-2026-73523 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-73523?

Not known from our data. No patch reference has been recorded for CVE-2026-73523, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-73523 affect?

CVE-2026-73523 affects COVESA Open1722 <= 0.9.2, AVTP/CAN listener implementations, Automotive AVB/infotainment devices using Open1722. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73523?

Apply vendor patch when released; restrict CAN/UDP access and filter AVTP stream inputs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
COVESA Open1722 <= 0.9.2AVTP/CAN listener implementationsAutomotive AVB/infotainment devices using Open1722
impact

Unauthenticated remote attacker can force CAN listener to transmit ~18KB of stack memory (~240 CAN frames) on the CAN bus, exposing sensitive memory contents.

action required

Patch when possible

affected versions
COVESA Open1722
  • affected<= 0.9.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free