How severe is CVE-2024-32896?

CVE-2024-32896 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-32896?

Affected package information for CVE-2024-32896 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2024-32896?

No fixed version has been published for CVE-2024-32896 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

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 0.2%, placing it in the 41th 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.

Which products and versions are affected by CVE-2024-32896?

CVE-2024-32896 affects google android. Check the affected-products list on this page against your deployed version to confirm exposure.

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

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

CISA KEV·Added 2024-06-13 — agencies required to remediate by 2024-07-04

CVE-2024-32896

HIGH

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…

Published

Jun 13, 2024

Updated

Oct 24, 2025

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk41th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-32896 in your stack?

O3 detects CVE-2024-32896 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works