In multiple functions of TaskFragmentOrganizerController.java, there is a possible activity token leak due to a logic error in the code.

published 2026-03-02 8mo ago modified 2026-06-17 4mo ago also EUVD-2025-208214

cvss: 7.7; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits: 0; none known

In multiple functions of TaskFragmentOrganizerController.java, there is a possible activity token leak due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Is CVE-2025-48635 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 8mo ago (2026-03-04)

Exploit prediction

0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	7.7	CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD	3.1	7.7	CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA	3.1	7.7	CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Google Android

Classification

Weakness

CWE-693 Protection Mechanism Failure
CWE-532 Insertion of Sensitive Information into Log File
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

source.android.com /docs/security/bulletin/2026/2026-03-01
vendor-advisory

Sources

CVE List CVE-2025-48635
NVD CVE-2025-48635

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.