EUVD-2026-78984
GHSA-gjhh-9vcv-f7xr
Severity by source
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Local unprivileged app, no UI (AV:L/AC:L/PR:N/UI:N); obtaining signatures and escalating gives C:H/I:H, but availability impact is not established by the description so A:L rather than A:H.
Primary rating from Vendor (Google_Devices).
CVSS VectorVendor: Google_Devices
Lifecycle Timeline
6DescriptionCVE.org
In multiple files, there is a possible way to obtain signatures due to type confusion. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
AnalysisAI
Local privilege escalation in Google Android and Pixel builds lets an already-installed, unprivileged app leverage a type-confusion flaw in multiple system files to obtain signature data it should not be able to reach, escalating to a higher-privileged context. The attack is purely local: per the CVSS vector (AV:L/PR:N/UI:N) no credentials, elevated privileges, or user interaction are required beyond getting a malicious app running on the device, though the attacker must first sideload or distribute that app through a store listing. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires local code execution on the device, i.e. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine but moderate-priority local privilege-escalation issue, not a mass-exploitation threat. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Primary fix: apply the vendor patch released with the September 2026 Pixel security bulletin (https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01) - an over-the-air Android security update that addresses the affected kernel/platform components; no specific patch version string is provided in the available data, so treat the 2026-09-01 (or later) security patch level as the remediation target and confirm the device's patch level under Settings > About phone. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, confirm the scope of affected Google Android and Pixel devices across managed and BYOD populations, verify that Android Enterprise policies already block installs from unknown sources, and re-baseline the mobile app inventory to identify any sideloaded or untrusted applications currently present. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
Same technique Privilege Escalation
View allShare
External POC / Exploit Code
Leaving vuln.today