Skip to content
IoT

CVE-2026-18281

8.0
High
EPSS 0.30%Aug 22, 2026

Bluetooth L2CAP heap overflow in Sony XAV-9500ES allows remote code execution.

common questions

Is CVE-2026-18281 being exploited?

Not confirmed. CVE-2026-18281 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.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-18281?

CVE-2026-18281 is rated High with a CVSS score of 8.0. 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-18281?

Not known from our data. No patch reference has been recorded for CVE-2026-18281, 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-18281 affect?

CVE-2026-18281 affects Sony XAV-9500ES infotainment systems, Bluetooth L2CAP stack on affected units. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-18281?

Unpair unknown devices, disable Bluetooth until vendor patch is applied; apply vendor patch when released.

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

executive summary
technical analysis
affected
Sony XAV-9500ES infotainment systemsBluetooth L2CAP stack on affected units
impact

Remote code execution via crafted L2CAP packets from a paired malicious Bluetooth device, enabling full device compromise.

action required

Immediate action required

affected versions
Sony XAV-9500ES
  • affected3.02.00

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