# CVE-2025-12047: Information disclosure in Scanner Pro

> An attacker on the same network can disclose sensitive user files from the Lenovo Scanner Pro application due to improper certificate validation.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/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:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-q4m2-33mj-c7h8

## What is CVE-2025-12047?

CVE-2025-12047 is a medium-severity vulnerability in Lenovo Scanner Pro, published on 12 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was reported in the Lenovo Scanner pro application during an internal security assessment that, under certain circumstances, could allow an attacker on the same logical network to disclose sensitive user files from the application.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2025-12047 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12047 is a medium-severity vulnerability in Lenovo Scanner Pro, published on 12 Nov 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-12047 in the wild and no public exploit code.

Affected product: Lenovo Scanner Pro. 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-12047/ (Markdown: https://insights.sbomify.com/CVE-2025-12047/index.md)
```

## Sources

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

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