dbcve.org
AndroidOperating system · Google

CVE-2025-48635

HIGH · 7.7 CVSS v3.1 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a local privilege escalation vulnerability in Android's TaskFragmentOrganizerController.java where activity tokens are inadvertently leaked due to a logic error in multiple functions. Activity tokens are security-sensitive handles used for inter-process communication in Android's window manager system; leaking them could allow a local attacker to hijack activity references and escalate privileges without any user interaction or additional execution privileges.

MitigationThe vulnerability requires fixing the logic error in TaskFragmentOrganizerController.java to prevent activity token leakage. This involves reviewing token handling code paths and ensuring tokens are not exposed to untrusted callers or stored in insecure contexts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 14.0= 15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version is exactly 14.0 or exactly 15.0 (not 14.0.x or 15.0.x patch levels)
  2. Verify Android build ID matches affected tags
    Run 'getprop ro.build.id' via ADB shell to get the build ID (e.g., UP1A.231005.007)
    Affected if The build ID corresponds to Android 14.0 or 15.0 factory images with the vulnerable TaskFragmentOrganizerController code
  3. Confirm TaskFragmentOrganizerController component presence
    Use 'dumpsys activity' via ADB shell to list activity task organizers, or check /system/framework/services.jar for the class
    Affected if The TaskFragmentOrganizerController class exists in the system and handles activity token operations
  4. Check if window manager task organization features are enabled
    Inspect ActivityTaskManager service configuration via 'dumpsys activity tasks' and look for any custom TaskFragmentOrganizer registrations
    Affected if Task organization features that use the affected controller are active on the device

A device is affected if it runs Android version 14.0 or 15.0 exactly and contains the vulnerable TaskFragmentOrganizerController implementation that leaks activity tokens.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The vulnerability requires fixing the logic error in TaskFragmentOrganizerController.java to prevent activity token leakage. This involves reviewing token handling code paths and ensuring tokens are not exposed to untrusted callers or stored in insecure contexts.

Recommended fix Moderate confidence
  1. 1. Ensure the device is running Android 14.0 (Build ID indicated in your device's settings) or Android 15.0
  2. 2. Navigate to Settings > Security & privacy > Security update on the Android device
  3. 3. Check for and install any available Android security patches
  4. 4. Verify the security patch level is at least the level that addresses CVE-2025-48635 (typically the latest available security update for your Android version)
  5. 5. After update installation, confirm the patch was successfully applied by re-checking the security patch date in Settings > About phone > Android version
Caveat Security patches for Android typically have minimal to no breaking changes as they address privilege escalation vulnerabilities in the platform

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48635 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data