Skip to main content
CVE-2025-60892VulnerabilityPublished

CVE-2025-60892: rpi-imager · n/a

Affects rpi-imagerSource CVE Database V5

0

Not known to be exploited · CVSS 6.8 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubraspberrypi/rpi-imagerpkg:github/raspberrypi/rpi-imagerOther threatsAffected
  • =1.9.6
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Avoid using Raspberry Pi Imager version 1.9.6 on Windows for OS customization until a patch is released. 2. Manually verify and clean the authorized_keys file on Raspberry Pi devices after imaging to ensure only intended keys are present. 3. Use alternative imaging tools or methods that do not exhibit this behavior, such as imaging on Linux or macOS if feasible. 4. Restrict access to Windows machines used for imaging to trusted personnel and secure them with strong authentication and endpoint protection. 5. Monitor Raspberry Pi devices for unauthorized SSH logins and implement network segmentation to limit potential lateral movement. 6. Stay updated with Raspberry Pi Foundation announcements for patches or updated imager versions addressing this vulnerability. 7. Educate users about the risks of SSH key management and the importance of verifying authorized_keys content post-imaging. 8. Consider disabling SSH key authentication temporarily if practical and use alternative secure access methods until the issue is resolved.

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.

References

Community reviews

Loading reviews…