CVE-2025-64696VulnerabilityPublished 9 Dec 2025

CVE-2025-64696: Android App "Brother iPrint&Scan" · Use of Cache Containing Sensitive Information

Affects Android App "Brother iPrint&Scan"Source CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.0 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Brother Industries, Ltd. Android App "Brother iPrint&Scan"	Affected <=6.13.7	Fixed in–

AI-suggested

1. Update the Brother iPrint&Scan app to the latest version once Brother Industries releases a patch addressing this vulnerability. 2. Until a patch is available, restrict installation of untrusted or unnecessary applications on Android devices used for printing/scanning to reduce the risk of malicious apps exploiting this flaw. 3. Enforce mobile device management (MDM) policies that limit app permissions and control access to external storage areas. 4. Educate users about the risks of installing apps from unverified sources and the importance of device hygiene. 5. Where possible, configure Android devices to use internal cache directories or encrypted storage for sensitive app data. 6. Monitor device logs and app behavior for unusual access patterns to cached data. 7. Consider isolating printing/scanning functions to dedicated devices with strict security controls to minimize exposure.

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.

Impact

For European organizations, the primary impact of this vulnerability is the potential unauthorized disclosure of sensitive information cached by the Brother iPrint&Scan app on Android devices. This could include print job metadata, scanned document previews, or user credentials cached temporarily. If employees use shared or unmanaged Android devices, malicious apps installed on these devices could exploit this vulnerability to access sensitive data, leading to privacy breaches or leakage of confidential business information. Although the vulnerability does not allow modification or disruption of app functionality, the confidentiality breach could undermine trust in document handling processes. Organizations in sectors handling sensitive documents, such as legal, finance, or government, may face compliance risks under GDPR if personal data is exposed. The low severity and requirement for local access limit the overall risk, but the vulnerability still represents a vector for insider threats or compromised devices within corporate environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Dec 2025, 10:36 UTC

Technical details

References

Community reviews

Related threats