# CVE-2025-26417: Missing authorization in Android

> A confused deputy flaw in Android's DownloadProvider allows local attackers to bypass user consent and access shared storage files without privileges.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2025
- **Updated:** 27 Aug 2025
- **Also known as:** A-304497167, ASB-A-304497167, GHSA-2j2g-7cwq-wpvg

## What is CVE-2025-26417?

CVE-2025-26417 is a medium-severity missing authorization vulnerability in Google Android, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In checkWhetherCallingAppHasAccess of DownloadProvider.java, there is a possible bypass of user consent when opening files in shared storage 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.

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere)

## Which versions are affected by CVE-2025-26417?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2025-26417?

Apply the vendor's patch.

## Is CVE-2025-26417 being exploited?

There is no known exploitation of CVE-2025-26417 in the wild and no public exploit code.

Public exploit code:

- https://github.com/uthrasri/CVE-2025-26417 (github_poc): https://github.com/uthrasri/CVE-2025-26417

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26417 and fix it if it is affected.

What it is: CVE-2025-26417 is a medium-severity missing authorization vulnerability in Google Android, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26417 in the wild and no public exploit code.

Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-26417/ (Markdown: https://insights.sbomify.com/CVE-2025-26417/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-26417
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-26417
- OSV: https://osv.dev/vulnerability/CVE-2025-26417

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-26417/
Summaries are generated and may contain mistakes; the official description above is the record.