CVE-2025-5476VulnerabilityPublished 21 Jun 2025Updated 23 Jun 2025

CVE-2025-5476: Sony XAV-AX8500 · Improper Isolation or Compartmentalization

Affects Sony XAV-AX8500Source CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Sony XAV-AX8500	Affected =2.00.01	Fixed in–

AI-suggested

Monitor for firmware updates or security patches from Sony addressing this vulnerability and apply them promptly once available.

Implement physical security controls to restrict unauthorized proximity to vehicles equipped with the Sony XAV-AX8500, such as secure parking areas or controlled access zones.

Disable Bluetooth connectivity on the device when not in use or when vehicles are parked in unsecured locations to reduce attack surface.

Employ Bluetooth monitoring tools capable of detecting unusual connection attempts or unauthorized devices within organizational premises.

Educate employees and fleet operators about the risks of Bluetooth vulnerabilities and encourage vigilance regarding suspicious device behavior.

Where possible, replace or upgrade devices running the affected firmware version 2.00.01 with newer versions or alternative products that have addressed this vulnerability.

Coordinate with automotive and fleet management teams to inventory affected devices and assess exposure within the organization.

Description

Sony XAV-AX8500 Bluetooth Improper Isolation Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected Sony XAV-AX8500 devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of ACL-U links. The issue results from the lack of L2CAP channel isolation. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26284.

Impact

For European organizations, the impact of this vulnerability depends largely on the prevalence of the Sony XAV-AX8500 device within their vehicle fleets or employee vehicles. Given that the device is an automotive multimedia receiver with Bluetooth connectivity, exploitation could allow attackers to bypass Bluetooth authentication and potentially access or manipulate the device’s Bluetooth communications. This could lead to unauthorized access to paired devices or data streams, potentially exposing sensitive information or enabling further attacks on connected systems. While the direct impact on critical infrastructure or enterprise IT systems is limited, organizations with large fleets of vehicles equipped with this device—such as logistics, transportation, or delivery companies—could face operational disruptions or data leakage risks. Additionally, the vulnerability could be leveraged as a foothold for lateral attacks within vehicles or to compromise driver safety systems if integrated. The lack of authentication requirement and no user interaction needed increases the risk of opportunistic attacks in environments where attackers can get physically close to vehicles, such as parking lots or loading docks. However, the overall impact remains medium due to the limited scope of the device and the low-level impact on confidentiality, integrity, and availability.

CWE-653Improper Isolation or Compartmentalization (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.
Architecture and Design
Break up privileges between different modules, objects, or entities. Minimize the interfaces between modules and require strong access control between them.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jun 2025, 12:52 UTC

WeaknessesCWE-653

Technical details

References

Community reviews

Related threats