Is CVE-2025-48640 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-48640 being exploited in the wild.

How severe is CVE-2025-48640?

High severity, with a CVSS score of 8, published 17 June 2026.

Is there a fix for CVE-2025-48640?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2025-48640 attacked?

It is attacked from the adjacent network, in an operating system.

Am I affected by CVE-2025-48640?

Check whether you run Google Android at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-48640: Google Android privilege escalation in System passkey pairing

CVE-2025-48640 · Severity: high · CVSS 8 · Published 2026-06-17

A security flaw in Android 17 could allow an unauthorized person physically near a device to bypass security checks during the passkey pairing process. This could allow an attacker to link a third-party device or credential to a user's account without their permission or interaction. If exploited, this could lead to unauthorized access to sensitive personal data or account takeover.

Technologies: Google Android. Vendors: Google.

Quick answers

Is CVE-2025-48640 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-48640 being exploited in the wild.
How severe is CVE-2025-48640?: High severity, with a CVSS score of 8, published 17 June 2026.
Which products and versions are affected?: Google Android 17.
Is there a fix for CVE-2025-48640?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2025-48640 attacked?: It is attacked from the adjacent network, in an operating system.
Am I affected by CVE-2025-48640?: Check whether you run Google Android at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in the System component of Android 17 arises from a missing permission check in multiple locations related to 3rd party passkey entry pairing. An attacker in proximal or adjacent range can exploit this flaw to achieve elevation of privilege without requiring any additional execution privileges or user interaction. The vulnerability is classified as CWE-862 (Missing Authorization). Google has addressed this in the Android 17 security release with a default security patch level of 2026-07-01.

Affected products

Google Android 17

Timeline

2026-06-16: advisory: Initial Android 17 Security Release Notes published
2026-06-17: disclosed: CVE-2025-48640 published to NVD

References

https://source.android.com/docs/security/bulletin/android-17

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.