basicsecurity.net
Proof, not just disclosure.
Threats / Android / CVE-2024-32896
CVE-2024-32896 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Android Pixel vulnerability

Android Pixel firmware vulnerability enabling privilege escalation, actively exploited in the wild.

Verdict

Today item — known-exploited.

CWE-783 privilege escalation in Pixel firmware allows attackers to gain elevated system access. Active exploitation in the wild indicates immediate risk to device security and user data.

CISA KEV Yes · 2024-06-133EPSS 0.0301 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-06-13).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.0301 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Android, Pixel. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-783 CWE-783.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
Gain code execution in unprivileged context on target Pixel device.
Business
User device security perimeter is compromised, enabling further malicious activity.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
Exploit firmware vulnerability to escalate privileges to system level.
Business
Attacker obtains unrestricted control over device hardware and software functions.
3

Lateral reach — past segmentation narrative 3

Attacker
Access sensitive user data, system credentials, and protected resources.
Business
Confidentiality breach exposes personal information and authentication tokens at scale.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 8 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Google_Devices (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by Google_DevicesCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.