Vulnerability in platform/frameworks/base (CVE-2025-48621)
Summary
Vulnerability in platform/frameworks/base (CVE-2025-48621). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 14:2025-12-01 or later.
Original description
The description as published by the source.
In DefaultTransitionHandler.java, there is a possible way to enable a tapjacking attack due to a insecure default. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-48621 has been found in platform/frameworks/base.
Successful exploitation can lead to full system takeover. CVSS score: 7.3/10.
What to do: upgrade platform/frameworks/base to 14:2025-12-01 or later.
If unsure, ask your IT team or search "platform/frameworks/base CVE-2025-48621" on the vendor's site.
CVE-2025-48621 (platform/frameworks/base) — CWE-1188 / CVSS v3 7.3
Attack vector: local
Patched: 14:2025-12-01 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1188) exists in platform/frameworks/base.
Check the vendor advisory for the affected versions of platform/frameworks/base.
Severity: High (CVSS 7.3/10). Successful exploitation can lead to full system takeover.
Update to 14:2025-12-01.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'platform/frameworks/base' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'platform/frameworks/base' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
platform/frameworks/baseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade platform/frameworks/base to 14:2025-12-01ステージング環境で 14:2025-12-01 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory source.android.com
- patch android.googlesource.com
- patch android.googlesource.com