# CVE-2025-55704: Information disclosure in Multiple MFPs

> Attackers can access hidden functionality to retrieve logs containing sensitive information from Brother and Konica Minolta multifunction printers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-wqr4-qgr2-f3rc

## What is CVE-2025-55704?

CVE-2025-55704 is a medium-severity vulnerability in Brother Industries, Ltd. Multiple MFPs, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hidden functionality issue exists in multiple MFPs provided by Brother Industries, Ltd., which may allow an attacker to obtain the logs of the affected product and obtain sensitive information within the logs.

Weakness: CWE-912 (Hidden Functionality)

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


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

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

## Is CVE-2025-55704 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55704 is a medium-severity vulnerability in Brother Industries, Ltd. Multiple MFPs, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55704 in the wild and no public exploit code.

Affected product: Brother Industries, Ltd. Multiple MFPs. 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-55704/ (Markdown: https://insights.sbomify.com/CVE-2025-55704/index.md)
```

## Sources

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

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