How severe is CVE-2025-21024?

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

Is CVE-2025-21024 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-21024?

CVE-2025-21024 affects Google Android. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-21024?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-21024 have an EU (EUVD) identifier?

Yes. CVE-2025-21024 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-23766.

When was CVE-2025-21024 published?

CVE-2025-21024 was published on 2025-08-06 and last updated on 2026-06-17.

CVE-2025-21024

CVE-2025-21024 is a low-severity vulnerability in Google Android with a CVSS 3.x base score of 3.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Low (CVSS 3.x base score 3.3)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-23766
Affected product: Google Android
Published: 2025-08-06
Last modified: 2026-06-17

Description

Use of Implicit Intent for Sensitive Communication in Smart View prior to Android 16 allows local attackers to access sensitive information.

Frequently asked questions

What is CVE-2025-21024?: Use of Implicit Intent for Sensitive Communication in Smart View prior to Android 16 allows local attackers to access sensitive information.
How severe is CVE-2025-21024?: CVE-2025-21024 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2025-21024 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-21024?: CVE-2025-21024 affects Google Android. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-21024?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-21024 have an EU (EUVD) identifier?: Yes. CVE-2025-21024 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-23766.
When was CVE-2025-21024 published?: CVE-2025-21024 was published on 2025-08-06 and last updated on 2026-06-17.

References

https://security.samsungmobile.com/serviceWeb.smsb?year=2025&month=08

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 →