Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2024-29748: Local privilege escalation in Google Pixel Firmware

Published Apr 5, 2024 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.68%53rd percentile
CISA KEVYesAdded Apr 4, 2024
In the wildActivePer CISA KEV
Vendor
Google
IdentifiersCVE-2024-29748CWE-840

CVE-2024-29748 is a logic-error vulnerability in Google Pixel Firmware that can permit a security bypass and local privilege escalation without additional execution privileges. Exploitation requires user interaction. The affected function and the specific security mechanism bypassed are not identified. The vulnerability has been exploited in targeted attacks and was included in forensic-vendor exploit chains requiring physical device access and custom malicious USB devices.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can elevate privileges locally on an affected Pixel device. CVE-2024-29748 was included in physical-access exploit chains that enabled attackers to unlock targeted mobile devices using custom malicious USB devices; that outcome is established for the chains rather than for this vulnerability in isolation.

Mitigation

If you can’t patch tonight, do this now.

Until patches are fully deployed, reduce opportunities for physical access to devices, restrict use of untrusted peripherals and USB accessories, and enforce device-handling controls for high-risk users. Where operationally feasible, limit or monitor USB-based interactions, maintain strong screen-lock and device management policies, and prioritize rapid patching for exposed or high-value Android and Pixel devices. Because exploitation has been associated with targeted attacks requiring device access, physical security controls are an important interim mitigation.

Remediation

Patch, then assume compromise.

Apply the April 5, 2024 security updates for affected Pixel firmware. A security patch level of 2024-04-05 or later addresses CVE-2024-29748. Install the latest available security updates on supported Pixel devices.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system
GooglePixelhardware
FAQ

Frequently asked questions

Is CVE-2024-29748 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 4, 2024.
Is there a public exploit for CVE-2024-29748?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2024-29748.
Is there a patch for CVE-2024-29748?
Apply the April 5, 2024 security updates for affected Pixel firmware. A security patch level of 2024-04-05 or later addresses CVE-2024-29748.
What products are affected by CVE-2024-29748?
Google Pixel and Google Android.
How severe is CVE-2024-29748?
CVE-2024-29748 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.68% (53rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.