In multiple functions of MediaProvider.java, there is a possible permission bypass due to a logic error in the code.
- Exploited
- No known exploitation
- Fix
- Fixed in 15, 16, 16-qpr2, 17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 15, 16, 16-qpr2, 17.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 15, 16, 16-qpr2, 17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In multiple functions of MediaProvider.java, there is a possible permission bypass due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
What to do
Upgrade to a fixed version: 15, 16, 16-qpr2, 17.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
17, 16-qpr2, 16, 15
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-59022
What does this mean?
A logic error in several functions of Android's MediaProvider.java allows a permission bypass, meaning an app can get access that its permissions should block. Google's bulletin classifies the issue as an information disclosure.Source: source.android.com
Am I affected, and how do I check?
Google's bulletin lists Android 15, 16, 16-qpr2 and 17 for this issue, and the sources give no further setup conditions. To check a device's Android version, open Settings > About phone, or run adb shell getprop ro.build.version.release, and compare the security patch level with the one in Google's bulletin.Source: source.android.com
What should I do about it?
Install the Android security update for the release line in use, which Google's bulletin lists as fixed for Android 15, 16, 16-qpr2 and 17. Check the device's update settings for a security patch level that includes CVE-2026-59022.Source: source.android.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data