# CVE-2025-64696: Information disclosure in Android App "Brother iPrint&Scan"

> Malicious apps can access sensitive files from the Brother iPrint&Scan app due to improper use of an external cache directory.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-545h-7g69-qc2h

## What is CVE-2025-64696?

CVE-2025-64696 is a medium-severity vulnerability in Android App "Brother iPrint&Scan", published on 9 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Android App "Brother iPrint&Scan" versions 6.13.7 and earlier improperly uses an external cache directory. If exploited, application-specific files may be accessed from other malicious applications.

Weakness: CWE-524 (Use of Cache Containing Sensitive Information)

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


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

No fix has been published for CVE-2025-64696 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-64696 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64696 is a medium-severity vulnerability in Android App "Brother iPrint&Scan", published on 9 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-64696 in the wild and no public exploit code.

Affected product: Android App "Brother iPrint&Scan". 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-64696/ (Markdown: https://insights.sbomify.com/CVE-2025-64696/index.md)
```

## Sources

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

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