Vulnerability

CVE-2021-39793

High· 7.8KEVCVSS7.8EPSS0%

.rules3/5

Google Pixel Out-of-Bounds Write Vulnerability

Google Pixel contains a possible out-of-bounds write due to a logic error in the code that could lead to local escalation of privilege.

Threat signal

88/100

Severe

Severity

high

CVSS

7.8

EPSS

Active

KEV

CISA KEV — actively exploited

1503d overdue

AffectedGoogle — Pixel

Added to KEV

2022-04-11

Federal patch due (BOD 22-01)

2022-05-02

Required action (CISA verbatim)

Apply updates per vendor instructions.

Vendor advisory + references

https://nvd.nist.gov/vuln/detail/CVE-2021-39793

CISA description: “Google Pixel contains a possible out-of-bounds write due to a logic error in the code that could lead to local escalation of privilege.”

CVSS

v3.1Open in FIRST calculator →

7.8/ 10HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack VectorLocalRequires local access — shell, console, or local app.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredLowStandard user privileges sufficient.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactHighTotal disclosure of sensitive data.
Integrity ImpactHighTotal compromise of integrity — full data modification possible.
Availability ImpactHighTotal loss of availability — full DoS possible.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

0.11%

probability of exploitation in next 30 days

p29

higher than 29% of all CVEs

3-day trend↑ 0pp

Low exploitation likelihood — defer if no other signals fire.

Vendor VEX

No VEX statements published for CVE-2021-39793. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCAct

Active exploitation with total impact on essential/support systems

exploitation: active
automatable: no
impact: total
mission: support

Lifecycle

2022-04-11Added to CISA KEVransomware: Unknown
2022-04-11Published
2022-05-02Federal patch due (BOD 22-01)
2026-06-12Last modified1 source

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.