How severe is CVE-2024-32896?

No CVSS score has been assigned to CVE-2024-32896 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-32896?

CVE-2024-32896 affects the following packages: platform/build/soong (Android), platform/frameworks/base (Android), platform/hardware/interfaces (Android), platform/system/sepolicy (Android), platform/frameworks/base (Android), platform/system/sepolicy (Android), platform/frameworks/base (Android), platform/system/sepolicy (Android), and 4 more. Ecosystems affected: Android.

How do I fix CVE-2024-32896?

Update platform/build/soong to 15-next:2024-09-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-32896 is resolved across your whole dependency graph.

How do I detect CVE-2024-32896 in my Android dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/build/soong, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-32896 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-32896 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2024-32896, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-32896?

CVE-2024-32896 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2024-32896 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-32896 (Android Pixel Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-06-13. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-07-04. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2024-32896?

CVE-2024-32896 is classified as CWE-670 (CWE-670), CWE-783 (CWE-783). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-32896 published, and has it been updated?

CVE-2024-32896 was published on September 1, 2024 and was last updated on October 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Android

CISA KEV · ACTIVELY EXPLOITED

CVE-2024-32896 — soong

CVE-2024-32896 is a CWE-670 vulnerability in platform/build/soong. It is in CISA's Known Exploited Vulnerabilities catalog (added 2024-06-13) — treat it as actively exploited and patch now. A fix is available for platform/build/soong — see the affected versions and patch details below.

Also known asA-324321147PUB-A-324321147

Published

Sep 1, 2024

Updated

Oct 23, 2026

Affected

12 pkgs

Patched

12 / 12

Exploits

2 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2024-06-13. Federal agencies were required to remediate by 2024-07-04.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-32896.

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

12 pkgs affected

📦platform/build/soong📦platform/frameworks/base📦platform/hardware/interfaces📦platform/system/sepolicy📦platform/frameworks/base📦platform/system/sepolicy📦platform/frameworks/base📦platform/system/sepolicy+4 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

12 total 12 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Android	`platform/build/soong`	≥ 15-next:0&&< 15-next:2024-09-01	15-next:2024-09-01
📦Android	`platform/frameworks/base`	≥ 15-next:0&&< 15-next:2024-09-01	15-next:2024-09-01
📦Android	`platform/hardware/interfaces`	≥ 15-next:0&&< 15-next:2024-09-01	15-next:2024-09-01
📦Android	`platform/system/sepolicy`	≥ 15-next:0&&< 15-next:2024-09-01	15-next:2024-09-01
📦Android	`platform/frameworks/base`	≥ 12:0&&< 12:2024-09-01	12:2024-09-01
📦Android	`platform/system/sepolicy`	≥ 12:0&&< 12:2024-09-01	12:2024-09-01

Affected Products

1 product · 1 configurations

androidgoogle

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

there is a possible way to bypass due to a logic error in the code. Thi…

source.android.comGoogle-sheetJun 2024

there is a possible way to bypass due to a logic error in the code. Thi…

cisa.govCISAJun 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/build/soong, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update platform/build/soong to 15-next:2024-09-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-32896 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-32896 in your dependencies?

Find it across Android, including transitive dependencies.

Scan my dependencies How O3 SCA works