CVE-2024-32896
there is a possible way to bypass due to a logic error in the code. This could lead to local...
there is a possible way to bypass 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 needed for exploitation.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
there is a possible way to bypass 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 needed for exploitation.
- Record
CVE-2024-32896- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-670, CWE-783
- Updated
- 2026-11-02
CVE List
there is a possible way to bypass 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 needed for exploitation.
- Record
CVE-2024-32896- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-783
- Updated
- 2026-11-02
EUVDEUVD-2024-30666
there is a possible way to bypass 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 needed for exploitation.
- Record
EUVD-2024-30666- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-qxgm-2hhj-rw7f
there is a possible way to bypass due to a logic error in the code. This could lead to local...
there is a possible way to bypass 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 needed for exploitation.
- Record
GHSA-qxgm-2hhj-rw7f- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-670, CWE-783
- Updated
- 2026-11-02
CISA KEV No score
Android Pixel Privilege Escalation Vulnerability
Android Pixel contains an unspecified vulnerability in the firmware that allows for privilege escalation.
- Record
CVE-2024-32896- Weakness
- CWE-783
- Updated
- 2026-11-02
OSVASB-A-324321147 No score
In rebootRecoveryWithCommand of RecoverySystemService.java, there is a possible way to bypass a factory reset 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 needed for exploitation.
- Record
ASB-A-324321147- Updated
- 2026-11-05
OSVPUB-A-324321147 No score
there is a possible way to bypass 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 needed for exploitation.
- Record
PUB-A-324321147- Updated
- 2026-11-05
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
platform/build/soongAndroid |
15-next:0 up to 15-next:2024-09-01, plus listed versions 15-next |
15-next:2024-09-01 |
platform/frameworks/baseAndroid |
15-next:0 up to 15-next:2024-09-01, plus listed versions 15-next |
15-next:2024-09-01 |
platform/hardware/interfacesAndroid |
15-next:0 up to 15-next:2024-09-01, plus listed versions 15-next |
15-next:2024-09-01 |
platform/system/sepolicyAndroid |
15-next:0 up to 15-next:2024-09-01, plus listed versions 15-next |
15-next:2024-09-01 |
platform/frameworks/baseAndroid |
12:0 up to 12:2024-09-01, plus listed versions 12 |
12:2024-09-01 |
platform/system/sepolicyAndroid |
12:0 up to 12:2024-09-01, plus listed versions 12 |
12:2024-09-01 |
platform/frameworks/baseAndroid |
12L:0 up to 12L:2024-09-01, plus listed versions 12L |
12L:2024-09-01 |
platform/system/sepolicyAndroid |
12L:0 up to 12L:2024-09-01, plus listed versions 12L |
12L:2024-09-01 |
platform/frameworks/baseAndroid |
13:0 up to 13:2024-09-01, plus listed versions 13 |
13:2024-09-01 |
platform/system/sepolicyAndroid |
13:0 up to 13:2024-09-01, plus listed versions 13 |
13:2024-09-01 |
Show 8 moreShow less
| Package | Affected | Fixed |
|---|---|---|
platform/frameworks/baseAndroid |
14:0 up to 14:2024-09-01, plus listed versions 14 |
14:2024-09-01 |
platform/system/sepolicyAndroid |
14:0 up to 14:2024-09-01, plus listed versions 14 |
14:2024-09-01 |
platform/build/soongAndroid |
14-next:0 up to 14-next:2024-06-05, plus listed versions 14-next |
14-next:2024-06-05 |
platform/frameworks/baseAndroid |
14-next:0 up to 14-next:2024-06-05, plus listed versions 14-next |
14-next:2024-06-05 |
platform/hardware/interfacesAndroid |
14-next:0 up to 14-next:2024-06-05, plus listed versions 14-next |
14-next:2024-06-05 |
platform/system/sepolicyAndroid |
14-next:0 up to 14-next:2024-06-05, plus listed versions 14-next |
14-next:2024-06-05 |
platform/frameworks/baseAndroid |
14:0 up to 14:2024-06-05, plus listed versions 14 |
14:2024-06-05 |
platform/system/sepolicyAndroid |
14:0 up to 14:2024-06-05, plus listed versions 14 |
14:2024-06-05 |
History
| Recorded | Changed | Sources |
|---|---|---|
| exploitation | ||
| first indexed | CVE List, EUVD, GitHub Advisories, CISA KEV, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2024-32896 is a high vulnerability (CVSS 7.8) in Android Pixel, published June 1, 2024. CISA lists it as known to be exploited, since June 13, 2024. EUVD reports exploitation since June 13, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 2.99%, the 87th percentile. Fixed in platform/build/soong 15-next:2024-09-01.
References
source.android.com/security/bulletin/pixel/2024-06-01
cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-32896
nvd.nist.gov/vuln/detail/CVE-2024-32896
github.com/advisories/GHSA-qxgm-2hhj-rw7f
android.googlesource.com/platform/system/sepolicy/+/92cbf8d4f18ccb2c488f50b7300bd6bfc33023aa