How severe is GHSA-2p6r-x3vv-xqm2?

GHSA-2p6r-x3vv-xqm2 has a CVSS score of 3.8/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2p6r-x3vv-xqm2?

GHSA-2p6r-x3vv-xqm2 affects the following packages: rpassword (crates.io). Ecosystems affected: crates.io.

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

Update rpassword to 7.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p6r-x3vv-xqm2 is resolved across your whole dependency graph.

How do I detect GHSA-2p6r-x3vv-xqm2 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rpassword, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2p6r-x3vv-xqm2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2p6r-x3vv-xqm2?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2p6r-x3vv-xqm2 can be triaged on real exposure rather than presence alone.

Is GHSA-2p6r-x3vv-xqm2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2p6r-x3vv-xqm2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2p6r-x3vv-xqm2 published, and has it been updated?

GHSA-2p6r-x3vv-xqm2 was published on May 6, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

LOW severity

GHSA-2p6r-x3vv-xqm2 — rpassword

LOW

GHSA-2p6r-x3vv-xqm2 is a low-severity (CVSS 3.8) vulnerability in rpassword. A fix is available for rpassword — see the affected versions and patch details below.

rpassword affected by partial password reveal when input is interrupted

Published

May 6, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀rpassword

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`rpassword`	all versions	7.5.0`cargo update -p rpassword --precise 7.5.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rpassword, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rpassword to 7.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p6r-x3vv-xqm2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2p6r-x3vv-xqm2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2p6r-x3vv-xqm2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-2p6r-x3vv-xqm2 in your dependencies?

O3 Security finds GHSA-2p6r-x3vv-xqm2 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works