BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-0093High confidence

This could lead to remote information disclosure with no additional execution privileges needed

Google · Android

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.31% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Google Android and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-25851

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

In handleBondStateChanged of AdapterService.java, there is a possible unapproved data access due to a missing permission check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

What

In handleBondStateChanged of AdapterService.java, there is a possible unapproved data access due to a missing permission check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

Why

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

In handleBondStateChanged of AdapterService.java, there is a possible unapproved data access due to a missing permission check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

Why

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Incorrect Permission Assignment for Critical Resource → obtain information outside the intended access boundary
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-732 ↗

CWE-732: Incorrect Permission Assignment for Critical Resource. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-732
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0477Android Patchday März 2025: Mehrere Schwachstellen

Ein Angreifer kann diese Schwachstellen ausnutzen, um seine Privilegien zu erweitern, einen Denial-of-Service-Zustand zu erzeugen, beliebigen Code auszuführen oder vertrauliche Informationen preiszugeben.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250828Security Bulletin 27 Aug 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 27 Aug 2025, published on 28 August 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0172Multiples vulnérabilités dans Google Android

.cve.org/CVERecord?id=CVE-2025-0079 Référence CVE CVE-2025-0080 https://www.cve.org/CVERecord?id=CVE-2025-0080 Référence CVE CVE-2025-0081 https://www.cve.org/CVERecord?id=CVE-2025-0081 Référence CVE CVE-2025-0082 https://www.cve.org/CVERecord?id=CVE-2025-0082 Référence CVE CVE-2025-0083 https://www.cve.org/CVERecord?id=CVE-2025-0083 Référence CVE CVE-2025-0084 https://www.cve.org/CVERecord?id=CVE-2025-0084 Référence CVE CVE-2025-0086 https://www.cve.org/CVERecord?id=CVE-2025-0086 Référence CVE CVE-2025-0087 https://www.cve.org/CVERecord?id=CVE-2025-0087 Référence CVE CVE-2025-0092 https://www.cve.org/CVERecord?id=CVE-2025-0092 Référence CVE CVE-2025-0093 https://www.cve.org/CVERecord?id=CVE-2025-0093 Référence CVE CVE-2025-20644 https://www.cve.org/CVERecord?id=CVE-2025-20644 Référence CVE CVE-2025-20645 https://www.cve.org/CVERecord?id=CVE-2025-20645 Référence CVE CVE-2025-22403 https://www.cve.org/CVERecord?id=CVE-2025-22403 Référence CVE CVE-2025-22404 https://www.cve.org/CVERecord?id=CVE-2025-22404 Référence CVE CVE-2025-22405 https://www.cve.org/CVERecord?id=CVE-2025-22405 Référence CVE CVE-2025-22406 https://www.cve.org/CVERecord?id=CVE-2025-22406 Référence CVE CVE-2025-22407 https://www.cve.org/CVERecord?id=CVE-2025-22407 Référence CVE CVE-2025-22408 https://www.cve.org/CVERecord?id=C

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-012819Google の Android における重要なリソースに対する不適切なパーミッションの割り当てに関する脆弱性

Google の Android には、重要なリソースに対する不適切なパーミッションの割り当てに関する脆弱性が存在します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2025-0072Kwetsbaarheden verholpen in Google Android en Samsung Mobile

De kwetsbaarheden bevinden zich in de Android-kernel en de ExternalStorageProvider.java, wat kan leiden tot lokale privilege-escalatie en remote code-executie. Daarnaast kunnen verschillende kwetsbaarheden remote aanvallers in staat stellen om denial-of-service te veroorzaken of gevoelige gegevens te benaderen. De kwetsbaarheden treffen verschillende versies van Android en Samsung-producten, wat onmiddellijke aandacht van beveiligingsbeheerders vereist. Google meldt informatie te hebben ontvangen dat de kwetsbaarheden met kenmerk CVE-2024-43093 en CVE-2024-50302 beperkt en gericht zijn misbruikt. Deze kwetsbaarheden bevinden zich respectievelijk in het Android Framework en in de Kernel en stellen een kwaadwillende in staat zich verhoogde rechten toe te kennen en toegang te krijgen tot gevoelige gegevens. Voor zover bekend moet voor succesvol misbruik de kwaadwillende het slachtoffer misleiden een malafide app te installeren.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
Android: 15, 14, 13, 12L, 12
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 26 Aug 2025 · Last source change 27 Aug 2025, 13:59 UTC · CWE-732 · Incorrect Permission Assignment for Critical Resource

CVE recordCVE.org · 5.1
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-25851
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-0093 · cve.blacktree.nl