dbcve.org
AndroidOperating system · Google

CVE-2025-22424

HIGH · 7.8 CVSS v3.1 Developing Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In multiple locations, there is a possible way to reveal images across users due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

An improper input validation vulnerability in multiple locations allows a local attacker to access or reveal images belonging to other users, enabling local privilege escalation without requiring additional execution privileges. User interaction is required for exploitation.

MitigationImplement proper input validation and authorization checks to ensure users can only access their own images; audit all image-related endpoints for similar access control issues.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:= 14.0= 15.0= 16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'
    Affected if Version equals 14.0, 15.0, or 16.0
  2. Verify multi-user or work profile functionality is enabled
    Check if multiple users or work profile exists via Settings > Accounts or 'adb shell pm list users'
    Affected if Multiple users or work profile is configured on the device
  3. Identify image retrieval components in use
    Review which apps or services handle image viewing, particularly system components like MediaProvider, Photo Picker, or gallery applications
    Affected if Image viewing applications that access shared media storage are in use
  4. Audit image request parameters
    Examine logs or use debugging tools to observe how image requests are processed, looking for improper validation of user ownership parameters
    Affected if Image requests do not validate that the requesting user owns the requested resource

A user is affected if their Android device runs version 14.0, 15.0, or 16.0 and they have multiple users or work profiles configured, allowing potential access to other users' images through the vulnerable image handling component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and authorization checks to ensure users can only access their own images; audit all image-related endpoints for similar access control issues.

Recommended fix Moderate confidence

Android 14.0 (update to latest available security patch), Android 15.0 (update to latest available security patch), Android 16.0 (update to latest available security patch)

  1. 1. Go to Settings > System > Software Update (or Settings > About Phone > System Update) on the affected Android device
  2. 2. Check for available updates by tapping 'Check for updates' or 'Download and install'
  3. 3. Download and install any available Android security update
  4. 4. After installation, verify the patch level by going to Settings > About Phone > Android version and confirming the Security patch level is updated
Caveat Standard Android security update risks apply - ensure backup of data before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22424 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22424 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data