CVE-2025-0082VulnerabilityPublished 26 Aug 2025

CVE-2025-0082: Google Android · Information disclosure

Affects Google AndroidSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

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

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

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

Attack Vector: Local
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: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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 26 Aug 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-25.

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 =12	Fixed in–

AI-suggested

To mitigate CVE-2025-0082, European organizations should: 1) Ensure all Android devices are updated promptly once official patches are released by Google, as no patches are currently linked. 2) Enforce strict device access controls to prevent unauthorized local access, including strong lock screen policies and biometric authentication. 3) Educate users about the risks of social engineering and the importance of not interacting with suspicious prompts that could trigger the vulnerability. 4) Limit the use of multi-user profiles on Android devices where possible, as the vulnerability exploits cross-user image disclosure. 5) Employ mobile device management (MDM) solutions to monitor and control app permissions and system service interactions. 6) Regularly audit devices for unusual access patterns or attempts to access images across user boundaries. 7) Consider restricting the use of affected Android versions in high-risk environments until patches are available. These steps go beyond generic advice by focusing on user interaction prevention, multi-user profile management, and device access controls specific to this vulnerability’s exploitation vector.

Description

In multiple functions of StatusHint.java and TelecomServiceImpl.java, there is a possible way to reveal images across users due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

Impact

For European organizations, the primary impact of CVE-2025-0082 is the potential unauthorized disclosure of sensitive images stored on Android devices used within the organization. This could include corporate-owned devices or employee personal devices used for work (BYOD). The confidentiality breach could expose sensitive personal or corporate information, potentially violating GDPR requirements for data protection and privacy. Although the attack requires local access and user interaction, insider threats or social engineering could facilitate exploitation. The vulnerability could be particularly impactful in sectors handling sensitive personal data such as healthcare, finance, and government agencies. Since Android is widely used across Europe, the risk is significant for organizations relying on Android devices for communication and data storage. The lack of known exploits in the wild suggests a window of opportunity for proactive mitigation before widespread exploitation occurs. However, the medium severity indicates that while the impact is serious, it is not critical or likely to cause immediate operational disruption.

CWE-610Externally Controlled Reference to a Resource in Another Sphere (opens in a new tab)
Class weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
Query Parameterization (opens in a new tab)
Attack patterns
XML Routing Detour Attacks (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 3 Sep 2025, 01:05 UTC

WeaknessesCWE-610

Technical details

References

Community reviews

Related threats