CVE-2025-26448 — Use of Uninitialized Variable in Frameworks Base

CWE-457 — Use of Uninitialized Variable5 documents5 sources
Severity
5.5MEDIUMNVD
EPSS
0.0%
top 99.63%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
2
Platform Frameworks BaseGoogle Android
Timeline
PublishedSep 4
Latest updateSep 5

Description

In writeToParcel of CursorWindow.cpp, there is a possible out of bounds read due to uninitialized data. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitability: 1.8 | Impact: 3.6

Affected Packages3 packages

▶Androidplatform/frameworks_base16-next:0 — 16-next:2025-06-01+3
▶CVEListV5google/android13, 14, 15+2
▶NVDgoogle/android13.0, 14.0, 15.0+2

Patches

Patch: android.googlesource.com ↗

🔴Vulnerability Details

3
GHSA
GHSA-rc6h-67x7-j653: In writeToParcel of CursorWindow↗2025-09-05
▶
CVEList
CVE-2025-26448: In writeToParcel of CursorWindow↗2025-09-04
▶
OSV
CVE-2025-26448: In writeToParcel of CursorWindow↗2025-06-01
▶

📋Vendor Advisories

1
Android
CVE-2025-26448: Android Security Bulletin 2025-06-01 CVE: CVE-2025-26448 Severity: HIGH Type: ID Affected AOSP versions: 13, 14, 15 References: A-309407957↗2025-06-01
▶
CVE-2025-26448 — Use of Uninitialized Variable | cvebase