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

This could lead to local escalation of privilege with no additional execution privileges needed

Google · Android

5.1MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.22% for the current model date.

Compensating controls

  • Restrict local access and enforce least privilege on affected hosts.
  • 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: As exposure requiresRemediation target: Within 365 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-26864

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

In onCreate of UninstallerActivity.java, there is a possible way to uninstall a different user's app due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

What

In onCreate of UninstallerActivity.java, there is a possible way to uninstall a different user's app due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Why

The product, while copying or cloning a resource, does not set the resource's permissions or access control until the copy is complete, leaving the resource exposed to other spheres while the copy is taking place.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In onCreate of UninstallerActivity.java, there is a possible way to uninstall a different user's app due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Why

The product, while copying or cloning a resource, does not set the resource's permissions or access control until the copy is complete, leaving the resource exposed to other spheres while the copy is taking place.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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
local access → Permission Race Condition During Resource Copy → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
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-689 ↗

CWE-689: Permission Race Condition During Resource Copy. The product, while copying or cloning a resource, does not set the resource's permissions or access control until the copy is complete, leaving the resource exposed to other spheres while the copy is taking place.

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

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.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.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-689
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-0937Android Patchday Mai 2025: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Google Android ausnutzen, um erhöhte Privilegien zu erlangen, beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen preiszugeben oder andere nicht spezifizierte Angriffe auszuführen.

Official advisory ↗
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-20250910Security Bulletin 10 SEP 2025

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

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

ecord?id=CVE-2024-49835 Référence CVE CVE-2024-49841 https://www.cve.org/CVERecord?id=CVE-2024-49841 Référence CVE CVE-2024-49842 https://www.cve.org/CVERecord?id=CVE-2024-49842 Référence CVE CVE-2024-49845 https://www.cve.org/CVERecord?id=CVE-2024-49845 Référence CVE CVE-2024-49846 https://www.cve.org/CVERecord?id=CVE-2024-49846 Référence CVE CVE-2024-49847 https://www.cve.org/CVERecord?id=CVE-2024-49847 Référence CVE CVE-2024-52939 https://www.cve.org/CVERecord?id=CVE-2024-52939 Référence CVE CVE-2025-0072 https://www.cve.org/CVERecord?id=CVE-2025-0072 Référence CVE CVE-2025-0077 https://www.cve.org/CVERecord?id=CVE-2025-0077 Référence CVE CVE-2025-0087 https://www.cve.org/CVERecord?id=CVE-2025-0087 Référence CVE CVE-2025-0427 https://www.cve.org/CVERecord?id=CVE-2025-0427 Référence CVE CVE-2025-20666 https://www.cve.org/CVERecord?id=CVE-2025-20666 Référence CVE CVE-2025-21453 https://www.cve.org/CVERecord?id=CVE-2025-21453 Référence CVE CVE-2025-21459 https://www.cve.org/CVERecord?id=CVE-2025-21459 Référence CVE CVE-2025-21467 https://www.cve.org/CVERecord?id=CVE-2025-21467 Référence CVE CVE-2025-21468 https://www.cve.org/CVERecord?id=CVE-2025-21468 Référence CVE CVE-2025-22425 https://www.cve.org/CVERecord?id=CVE-2025-22425 Référence CVE CVE-2025-26420 https://www.cve.org/CVERecord?id=CVE

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

.cve.org/CVERecord?id=CVE-2025-0075 Référence CVE CVE-2025-0078 https://www.cve.org/CVERecord?id=CVE-2025-0078 Référence CVE CVE-2025-0079 https://www.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-2

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-013270Google の Android におけるリソースコピー時のアクセス権競合状態に関する脆弱性

Google の Android には、リソースコピー時のアクセス権競合状態に関する脆弱性が存在します。

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

De kwetsbaarheden bevinden zich onderandere in de Keymaster trustlet, SmartManagerCN en FreeType. De kwetsbaarheden stellen een lokale aanvaller in staat om code uit te voeren op het apparaat en code uit te voeren met de rechten van SmartManagerCN. Google meldt informatie te hebben ontvangen dat de kwetsbaarheid met kenmerk CVE-2025-27363 beperkt en gericht als zeroday is misbruikt. Deze kwetsbaarheid bevindt zich in FreeType en stelt een kwaadwillende in staat code uit te voeren middels een heap buffer overflow.

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
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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 4 Sept 2025 · Last source change 4 Sept 2025, 19:47 UTC · CWE-689 · Permission Race Condition During Resource Copy

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-26864
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-0087 · cve.blacktree.nl