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

Android Pixel vulnerability

Android Pixel Framework contains an information disclosure vulnerability where insufficient UI notifications allow local attackers to hide foreground service notifications and access sensitive information.

Verdict

Today item — known-exploited.

A local attacker can exploit misleading UI in the Framework component to conceal foreground service notifications, enabling unauthorized access to sensitive information on affected Pixel devices.

CISA KEV Yes · 2024-03-053EPSS 0.00264 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
source.android.com ↗cisa.gov ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-03-05).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00264 — 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: Android, Pixel. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-200 Information Exposure — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-200 · Information ExposureAuthorization / access control
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 craft a malicious application that exploits the Framework's UI notification handling to hide my foreground service from the user.
Business
User awareness and control over running services is compromised, reducing transparency of device activity.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute my hidden service to access sensitive information without user knowledge or consent.
Business
Customer data confidentiality is breached, creating liability and reputational damage.
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)
  • 2 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.