How severe is GHSA-vgr2-r5hm-f6gf?

No CVSS score has been assigned to GHSA-vgr2-r5hm-f6gf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vgr2-r5hm-f6gf?

GHSA-vgr2-r5hm-f6gf affects the following packages: sha-rst (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-vgr2-r5hm-f6gf?

The records we use list no patched version of sha-rst for GHSA-vgr2-r5hm-f6gf. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-vgr2-r5hm-f6gf in my crates.io dependencies?

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

How do I mitigate GHSA-vgr2-r5hm-f6gf 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.

Is GHSA-vgr2-r5hm-f6gf actively exploited in the wild?

No public exploit code has been indexed for GHSA-vgr2-r5hm-f6gf 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-vgr2-r5hm-f6gf published, and has it been updated?

GHSA-vgr2-r5hm-f6gf was published on February 12, 2026 and was last updated on February 13, 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

`sha-rst` was removed from crates.io for malicious codeGHSA-vgr2-r5hm-f6gf

GHSA-vgr2-r5hm-f6gf is a security vulnerability in sha-rst. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0151

Published

Feb 12, 2026

Updated

Feb 13, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Feb 13, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀sha-rst

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

This crate was used as a dependency by finch_cli_rust and finch-rst and contained a malware payload to exfiltrate credentials.

The malicious crate had 1 version published on 2025-12-08 and had been downloaded 22 times. Other than the other crates above that were part of the attack, no other crates depedended on this crate.

Thanks to Matthias Zepper of NGI Sweden for reporting this to the crates.io team!

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`sha-rst`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sha-rst, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of sha-rst for GHSA-vgr2-r5hm-f6gf. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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.

Frequently Asked Questions

This crate was used as a dependency by `finch_cli_rust` and `finch-rst` and contained a malware payload to exfiltrate credentials. The malicious crate had 1 version published on 2025-12-08 and had been downloaded 22 times. Other than the other crates above that were part of the attack, no other crates depedended on this crate. Thanks to Matthias Zepper of [NGI Sweden](https://ngisweden.scilifelab.se/) for reporting this to the crates.io team!

O3 Security · Impact-Aware SCA

Is GHSA-vgr2-r5hm-f6gf in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works