CVE-2025-32330VulnerabilityPublished 4 Sep 2025

CVE-2025-32330: Google Android · Information disclosure

Affects Google AndroidSource CVE Database V5

Not known to be exploited · CVSS 5.7 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.7Medium

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

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

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

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

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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Sep 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 2026-10-26.

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
Google Android	Affected =15 =14 =13	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Monitor for official patches or updates from Google addressing CVE-2025-32330 and prioritize timely deployment on all affected Android devices (versions 13-15). 2) Disable Auracast Bluetooth LE broadcasting on Android devices in sensitive or high-risk environments where confidential audio is transmitted, until patches are available. 3) Implement physical security controls to limit unauthorized proximity to devices broadcasting Auracast streams, such as controlled access zones or Bluetooth signal containment measures. 4) Educate users about the risk of nearby attackers intercepting Auracast audio and encourage cautious use of Bluetooth audio broadcasting in public or unsecured areas. 5) Employ network monitoring tools capable of detecting unusual Bluetooth LE broadcast activity or unauthorized devices in proximity. 6) Consider alternative secure audio streaming technologies with stronger encryption and authentication mechanisms if Auracast usage is critical. These steps go beyond generic advice by focusing on controlling physical proximity risks and managing Auracast usage policies specifically.

Description

In generateRandomPassword of LocalBluetoothLeBroadcast.java, there is a possible way to intercept the Auracast audio stream due to an insecure default value. This could lead to remote (proximal/adjacent) information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Impact

For European organizations, the impact of CVE-2025-32330 primarily concerns confidentiality breaches of audio data transmitted via Auracast Bluetooth LE broadcasts. Organizations using Android devices (versions 13-15) for Auracast-enabled audio streaming in sensitive environments—such as corporate meetings, healthcare settings, or government facilities—could have confidential conversations or audio content intercepted by nearby attackers. Since no user interaction or elevated privileges are required, the risk of unnoticed eavesdropping is significant in public or semi-public spaces. This could lead to leakage of proprietary information, personal data, or other sensitive audio content. However, the impact is limited by the need for physical proximity to the target device due to Bluetooth range constraints. The vulnerability does not affect data integrity or availability, so it does not enable tampering or denial of service. Nevertheless, the confidentiality breach could undermine trust in Bluetooth Auracast technology and Android devices in professional environments across Europe.

CWE-1188Initialization of a Resource with an Insecure Default (opens in a new tab)
Base weakness
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (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 11 Sep 2025, 20:16 UTC

WeaknessesCWE-1188

Technical details

References

Community reviews

Related threats