basicsecurity.net
Proof, not just disclosure.
Threats / Google / CVE-2021-39793
CVE-2021-39793 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Google Pixel vulnerability

Google Pixel contains an out-of-bounds write vulnerability due to logic error, enabling local privilege escalation.

Verdict

Today item — known-exploited.

A logic error in Pixel code permits out-of-bounds memory writes, allowing local attackers to escalate privileges. The vulnerability has been exploited in the wild.

CISA KEV Yes · 2022-04-113EPSS 0.00726 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
docs.google.com ↗cisa.gov ↗raw.githubusercontent.co ↗ti.qianxin.com ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-11).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00726 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
Affected: Google, Pixel. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-787 · Out-of-bounds WriteMemory safety
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
I gain code execution on the target Pixel device through an initial compromise or physical access.
Business
User device security is compromised, exposing personal data and system integrity.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I craft input that triggers the logic error, writing data beyond allocated buffer boundaries in kernel or privileged memory.
Business
Memory corruption creates unpredictable system behavior and potential data loss.
3

Lateral reach — past segmentation narrative 3

Attacker
I leverage the out-of-bounds write to overwrite privilege-related structures or execute arbitrary code at elevated privilege level.
Business
Attacker gains system-level control, bypassing security boundaries and access controls.
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)
  • 5 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by google_android (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_androidCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.