How severe is CVE-2024-32896?

CVE-2024-32896 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2024-32896 being actively exploited?

Yes. CVE-2024-32896 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2024-06-13, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2024-32896?

CVE-2024-32896 affects Google Android. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-32896?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2024-32896 have an EU (EUVD) identifier?

Yes. CVE-2024-32896 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-30666. It is also flagged as exploited in the EUVD (since 2024-06-13).

When was CVE-2024-32896 published?

CVE-2024-32896 was published on 2024-06-13 and last updated on 2026-06-17.

CVE-2024-32896

CVE-2024-32896 is a high-severity vulnerability in Google Android with a CVSS 3.x base score of 7.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2024-06-13). The underlying weakness is classified as CWE-670.

Key facts

Severity: High (CVSS 3.x base score 7.8)
EPSS exploit prediction: 3% (86th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2024-06-13)
EU (EUVD) id: EUVD-2024-30666
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2024-06-13)
Weakness: CWE-670
Affected product: Google Android
Published: 2024-06-13
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2024-32896?: 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.
How severe is CVE-2024-32896?: CVE-2024-32896 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-32896 being actively exploited?: Yes. CVE-2024-32896 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2024-06-13, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2024-32896?: CVE-2024-32896 affects Google Android. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-32896?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2024-32896 have an EU (EUVD) identifier?: Yes. CVE-2024-32896 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-30666. It is also flagged as exploited in the EUVD (since 2024-06-13).
When was CVE-2024-32896 published?: CVE-2024-32896 was published on 2024-06-13 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:o:google:android:-:*:*:*:*:*:*:*

More vulnerabilities in Google Android

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2015-8073 — Critical (CVSS 10.0): mediaserver in Android 4.4 and 5.1 before 5.1.1 LMY48X allows remote attackers to execute arbitrary code or cause a…
CVE-2015-8072 — Critical (CVSS 10.0): mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute…
CVE-2015-6610 — Critical (CVSS 10.0): libstagefright in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a…
CVE-2015-6609 — Critical (CVSS 10.0): libutils in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or…

All CVEs affecting Google Android →

Other CWE-670 vulnerabilities

CVE-2025-43359 — Critical (CVSS 9.8): A logic issue was addressed with improved state management. This issue is fixed in iOS 18.7 and iPadOS 18.7, iOS 26 and…
CVE-2022-25745 — Critical (CVSS 9.8): Memory corruption in modem due to improper input validation while handling the incoming CoAP message
CVE-2020-1914 — Critical (CVSS 9.8): A logic vulnerability when handling the SaveGeneratorLong instruction in Facebook Hermes prior to commit…
CVE-2020-17466 — Critical (CVSS 9.8): Turcom TRCwifiZone through 2020-08-10 allows authentication bypass by visiting manage/control.php and ignoring 302…
CVE-2019-17192 — Critical (CVSS 9.8): The WebRTC component in the Signal Private Messenger application through 4.47.7 for Android processes videoconferencing…
CVE-2026-55276 — Critical (CVSS 9.1): Always-Incorrect Control Flow Implementation vulnerability in Apache Tomcat meant that special roles and empty…

Browse all CWE-670 vulnerabilities →