In checkWhetherCallingAppHasAccess of DownloadProvider.java, there is a possible information leak due to a confused deputy.
Affects Google Android's Framework component, with fixes listed for Android 14, 15, 16, 16-qpr2 and 17.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 14, 15, 16, 16-qpr2, 17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 14, 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 14, 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 checkWhetherCallingAppHasAccess of DownloadProvider.java, there is a possible information leak due to a confused deputy. 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: 14, 15, 16, 16-qpr2, 17.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
17, 16-qpr2, 16, 15, 14
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-55264
What does this mean?
The bug is in checkWhetherCallingAppHasAccess in DownloadProvider.java. A confused deputy flaw can let an app receive information it should not be able to see, which is an information disclosure issue.Source: source.android.com
Am I affected, and how do I check?
The advisory lists the Framework component for Android 14, 15, 16, 16-qpr2 and 17. To check a device, look at the Android version under Settings > About phone, and compare its security patch level with the Android security bulletin for that month.Source: source.android.com
What should I do about it?
Install the Android update that includes the fix for your version, which the advisory lists as Android 14, 15, 16, 16-qpr2 or 17. Check for system updates under Settings > System > Software update.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