CVE-2025-48616

Local information disclosure via stale lockdown state

Published Jun 1, 2026 · Updated Jun 1, 2026

Information disclosure in Android 14, 15, 16, and 16-qpr2 allows local users to bypass lockdown mode through screen pinning. KeyguardViewMediator consults LockPatternUtils for lockdown state even though it can be out of sync with KeyguardUpdateMonitor's strong-auth tracker, so the keyguard can fail to appear after a pinned app and lockdown are combined. Low-privilege local access and an already pinned app are sufficient; no user interaction is required, and the reported consequence is reading information otherwise protected by the lock screen.

CVSS severity3.3
Low
EPSS probability0.11%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Android 14, 15, 16, and 16-qpr2 allows local users to bypass lockdown mode through screen pinning. KeyguardViewMediator consults LockPatternUtils for lockdown state even though it can be out of sync with KeyguardUpdateMonitor's strong-auth tracker, so the keyguard can fail to appear after a pinned app and lockdown are combined. Low-privilege local access and an already pinned app are sufficient; no user interaction is required, and the reported consequence is reading information otherwise protected by the lock screen.

The record

CVE
CVE-2025-48616
Published
Jun 1, 2026
Updated
Jun 1, 2026
Vendor
Go standard library
Product
Android
Classifications
T1005
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Jun 1, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 1, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=14
  2. Affected versionversion=15
  3. Affected versionversion=16
  4. Affected versionversion=16-qpr2

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

Go standard library · Androidversion=14; version=15; version=16; version=16-qpr2

Published CVSS scores

3.3CISA-ADPCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1005Data from Local System

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo