# CVE-2025-60892: Information disclosure in n/a

> Raspberry Pi Imager unintentionally restores deleted SSH keys, potentially allowing unauthorized access to devices via unintended authentication paths.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/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:** No
- **Published:** 3 Nov 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-cr7p-v4gj-9p32

## What is CVE-2025-60892?

CVE-2025-60892 is a medium-severity vulnerability in n/a, published on 3 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in Raspberry Pi Imager version 1.9.6 for Windows, affecting its OS customization feature. The imager's 'public-key authentication' setting unintentionally re-adds a user's id_rsa.pub key from their local Windows machine to the authorized_keys file on the Raspberry Pi, even after the user explicitly deletes the key from the user interface. This creates an unintended attack surface, as it could allow an attacker to use a different key than the intended one to login to the device.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-60892 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60892 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60892 is a medium-severity vulnerability in n/a, published on 3 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60892 exists.

Affected product: n/a. 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-60892/ (Markdown: https://insights.sbomify.com/CVE-2025-60892/index.md)
```

## Sources

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

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