# GHSA-2p6r-x3vv-xqm2: rpassword affected by partial password reveal when input is interrupted

> An attacker with local access can recover partial passwords if the input process is interrupted, affecting applications using the rpassword library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 May 2026

## What is GHSA-2p6r-x3vv-xqm2?

GHSA-2p6r-x3vv-xqm2 is a vulnerability in rpassword, published on 6 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

rpassword maintainers were made aware of a possible issue with a partial password reveal when input is interrupted.

To quote @squell:

> @conradkleinespel I've confirmed this problem with SequoiaPGP, which I think uses rpassword, e.g.:
>
> Suppose we use pkill -9 sq in a different terminal right after the password has been typed in:
>
> $ sq key generate --userid "barf" --with-password
> Enter password to protect the key: Killed
> $ hello^C
>
> Where the password I typed in is "hello".

This has been fixed in version v7.5.0 and above.

## Which versions are affected by GHSA-2p6r-x3vv-xqm2?

2 open source packages ship an affected version, including rpassword.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rpassword` | crates.io | All versions | 7.5.0 |
| `rpassword` | crates.io | All versions | 7.5.0 |

## How do I fix GHSA-2p6r-x3vv-xqm2?

Upgrade rpassword to 7.5.0 or later.

## Is GHSA-2p6r-x3vv-xqm2 being exploited?

There is no known exploitation of GHSA-2p6r-x3vv-xqm2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2p6r-x3vv-xqm2 and fix it if it is affected.

What it is: GHSA-2p6r-x3vv-xqm2 is a vulnerability in rpassword, published on 6 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-2p6r-x3vv-xqm2 in the wild and no public exploit code.

Affected packages and fixed versions:
- rpassword (crates.io): affected all versions; fixed in 7.5.0
- rpassword (crates.io): affected all versions; fixed in 7.5.0

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/GHSA-2p6r-x3vv-xqm2/ (Markdown: https://insights.sbomify.com/GHSA-2p6r-x3vv-xqm2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2p6r-x3vv-xqm2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2p6r-x3vv-xqm2/
Summaries are generated and may contain mistakes; the official description above is the record.