How severe is CVE-2024-29748?

CVE-2024-29748 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2024-29748 being actively exploited?

Yes. CVE-2024-29748 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2024-04-04, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2024-29748?

CVE-2024-29748 affects Google Android. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-29748?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2024-29748 have an EU (EUVD) identifier?

Yes. CVE-2024-29748 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-26743. It is also flagged as exploited in the EUVD (since 2024-04-04).

When was CVE-2024-29748 published?

CVE-2024-29748 was published on 2024-04-05 and last updated on 2026-06-17.

CVE-2024-29748

CVE-2024-29748 is a high-severity vulnerability in Google Android with a CVSS 3.x base score of 7.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2024-04-04). The underlying weakness is classified as CWE-755.

Key facts

Severity: High (CVSS 3.x base score 7.8)
EPSS exploit prediction: 1% (48th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2024-04-04)
EU (EUVD) id: EUVD-2024-26743
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2024-04-04)
Weakness: CWE-755
Affected product: Google Android
Published: 2024-04-05
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2024-29748?: 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.
How severe is CVE-2024-29748?: CVE-2024-29748 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-29748 being actively exploited?: Yes. CVE-2024-29748 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2024-04-04, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2024-29748?: CVE-2024-29748 affects Google Android. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-29748?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2024-29748 have an EU (EUVD) identifier?: Yes. CVE-2024-29748 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-26743. It is also flagged as exploited in the EUVD (since 2024-04-04).
When was CVE-2024-29748 published?: CVE-2024-29748 was published on 2024-04-05 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:o:google:android:*:*:*:*:*:*:*:*

More vulnerabilities in Google Android

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2015-8073 — Critical (CVSS 10.0): mediaserver in Android 4.4 and 5.1 before 5.1.1 LMY48X allows remote attackers to execute arbitrary code or cause a…
CVE-2015-8072 — Critical (CVSS 10.0): mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute…
CVE-2015-6610 — Critical (CVSS 10.0): libstagefright in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a…
CVE-2015-6609 — Critical (CVSS 10.0): libutils in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or…

All CVEs affecting Google Android →

Other CWE-755 (Improper Handling of Exceptional Conditions) vulnerabilities

CVE-2025-34193 — Critical (CVSS 9.8): Vasion Print (formerly PrinterLogic) Virtual Appliance Host versions prior to 25.1.102 and Application versions prior…
CVE-2025-10156 — Critical (CVSS 9.8): An Improper Handling of Exceptional Conditions vulnerability in the ZIP archive scanning component of mmaitre314…
CVE-2021-42142 — Critical (CVSS 9.8): An issue was discovered in Contiki-NG tinyDTLS through master branch 53a0d97. DTLS servers mishandle the early use of a…
CVE-2021-42141 — Critical (CVSS 9.8): An issue was discovered in Contiki-NG tinyDTLS through 2018-08-30. One incorrect handshake could complete with…
CVE-2023-38406 — Critical (CVSS 9.8): bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a "flowspec overflow."
CVE-2022-23121 — Critical (CVSS 9.8): This vulnerability allows remote attackers to execute arbitrary code on affected installations of Netatalk.…

Browse all CWE-755 (Improper Handling of Exceptional Conditions) vulnerabilities →