CVE-2024-29748
HighExploitedPublic exploitthere is a possible way to bypass due to a logic error in the code.
Published Apr 5, 2024 · Updated Oct 14, 2026 · Also known as A-318507188, PUB-A-318507188
Key Facts
Patch immediately- CVE-2024-29748 is a high-severity vulnerability (CVSS 7.8 v3.1) affecting Android (Google), :unknown: (android).
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Apr 2, 2024. Public exploit code is available.
- EPSS estimates a 0.7% probability of exploitation in the next 30 days.
- Fixed versions are available, including :unknown: Pixel-family specific:2024-04-05, Android 2024-04-05.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
7.8
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
0.7%
Higher than 51.2% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2024-29748 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
there is a possible way to bypass due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Apr 4, 2024 | Apr 25, 2024 | Not reported |
| Industry KEV feed | Apr 2, 2024 | Apr 25, 2024 | Not reported |
| CIRCL KEV | Apr 4, 2024 | Apr 25, 2024 | Not reported |
| ENISA EUVD | Apr 4, 2024 | n/a | Not reported |
Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Affected Products
3 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| AndroidGoogle | >= Android kernel | 2024-04-05 |
| :unknown:android | >= Pixel-family specific:0 | Pixel-family specific:2024-04-05 |
Patched Releases
:unknown:
Pixel-family specific:2024-04-05
Android
2024-04-05
Timeline
Added to Industry KEV feed
Apr 2, 2024
Added to CISA KEV
Apr 4, 2024
Added to CIRCL KEV
Apr 4, 2024
Added to ENISA EUVD
Apr 4, 2024
Publicly disclosed
Apr 5, 2024
Last updated
Oct 14, 2026
Weakness Type
- CWE-280 Improper Handling of Insufficient Permissions or Privileges
- CWE-755 Improper Handling of Exceptional Conditions
References
- advisoryhttps://source.android.com/security/bulletin/2024-04-01
- advisoryhttps://source.android.com/security/bulletin/pixel/2024-04-01
- advisoryhttps://twitter.com/GrapheneOS/status/1775308208472813609
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
FAQ
Common Questions.
there is a possible way to bypass due to a logic error in the code.
Affected: Android (Google) versions >= Android kernel; :unknown: (android) versions >= Pixel-family specific:0. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Apr 2, 2024.
Yes. It was added on Apr 4, 2024 with a federal remediation due date of Apr 25, 2024.
Public exploit code is available.
Fixed versions are available, including :unknown: Pixel-family specific:2024-04-05, Android 2024-04-05.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2024-29748 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo