Is CVE-2024-32896 actively exploited?

Yes. KEV Intelligence tracks CVE-2024-32896 as a known exploited vulnerability. Confidence is confirmed.

What exploitation activity has KEV Intelligence observed?

KEV Intelligence has not yet recorded sensor-observed exploitation attempts for CVE-2024-32896. Our sensors continue to monitor for activity targeting this CVE.

Which versions are affected?

CVE-2024-32896 affects Google Android. Reported affected versions include 0 to < 2024-06-01 and Android kernel.

Yes. CVE-2024-32896 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

Vulnerability report

Exploited in the wild Confirmed confidence In CISA KEV

CVE-2024-32896

Q: What is CVE-2024-32896?

CVE-2024-32896 is an unauthenticated vulnerability affecting Google Android. 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.

Q: How should organizations remediate it?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Q: Is it in CISA KEV?

Yes. CVE-2024-32896 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

Android

Google / Android · affected before 2024-06-01

View live feed Monitor via API Watch CVE

Severity: CVSS 7.8 · High
Confidence: Confirmed
Exploit status: Exploited in the wild
EPSS: 3.0%
First observed: —
Last observed: —

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2024-32896 is an unauthenticated vulnerability affecting Google Android. 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...

Is it exploited?

Yes. KEV Intelligence tracks this CVE as a known exploited vulnerability. Confidence is confirmed.

Who is affected?

Google / Android affected before 2024-06-01.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

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

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.

Vendor Product Affected Status

google android Before 2024-06-01 Affected

Google Android Android kernel Affected

Published: 13 Jun 2024
Exploitation Reported: 13 Jun 2024
Attack vector: Local
Complexity: Low
Privileges: None
User interaction: Required

CVE References

CVE Record CVE.org · CVE Record https://www.cve.org/CVERecord?id=CVE-2024-32896
source.android.com/security/bulletin/pixel/2024-06-01 source.android.com · CVE Record https://source.android.com/security/bulletin/pixel/2024-06-01

Exploitation evidence

Why KEV Intelligence marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CISA

Recorded 13 Jun 2024

Independent exploitation attestation added to the KEV Intelligence record.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the KEV Intelligence Pro API.

Learn about Pro API access

Source	Added
CISA First	2024-06-13 00:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets: 0
User-Agents: 0

Raw values available in Pro and Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No KEV Intelligence virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

7.8 High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

3.0%

Weaknesses

Operator Precedence Logic Error CWE-783

Recent mention · Google Threat Intelligence

Written by: Casey Charrier, James Sadowski, Clement Lecigne, Vlad Stolyarov Executive Summary Google Threat Intelligence Group (GTIG) tracked 75...

Written by: Casey Charrier, James Sadowski, Clement Lecigne, Vlad Stolyarov Executive Summary Google Threat Intelligence Group (GTIG) tracked 75 zero-day vulnerabilities exploited in the wild in 2024, a decrease from the number we identified in 2023 (98 vulnerabilities), but...

Read full advisory

Timeline

From disclosure to observed exploitation

13 Jun 2024
CVE published

Vulnerability disclosed publicly
13 Jun 2024
Added to CISA KEV

Listed in the CISA Known Exploited Vulnerabilities catalog
19 Apr 2024
CVE ID reserved

Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

View Pro pricing Read API docs

Evidence confidence and provenance
First-party sensor telemetry
PoC and scanner references
Affected versions and enrichment
Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2024-32896

Free JSON includes basic KEV fields

{
  "cve_id": "CVE-2024-32896",
  "confidence": "Confirmed",
  "cvss_score": 7.8,
  "cvss_estimated": false,
  "epss_score": 0.0301,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}

Early warning alerts

Get alerts on high-impact exploitation

Receive curator-selected alerts when exploitation activity warrants attention. Each alert includes the evidence and context needed to decide what requires attention now.