Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-6v2j-vr4h-f632 finch_cli_rust

GHSA-6v2j-vr4h-f632 is a security vulnerability in finch_cli_rust. No vendor fix is recorded yet; mitigation options are listed below.

`finch_cli_rust` was removed from crates.io for malicious code

Also known asRUSTSEC-2025-0152
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
🦀finch_cli_rust

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 attempts to typosquat the existing crate finch_cli to steal credentials from local files.

The malicious crate had 1 version published on 2025-12-08 and had been downloaded 18 times. There were no crates depending on this crate on crates.io.

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

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🦀crates.iofinch_cli_rustall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Remediation status

    No patched version of finch_cli_rust has shipped for GHSA-6v2j-vr4h-f632 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. 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.

  4. How O3 protects you

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

Tailored to GHSA-6v2j-vr4h-f632. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This attempts to typosquat the existing crate [`finch_cli`](https://crates.io/crates/finch_cli) to steal credentials from local files. The malicious crate had 1 version published on 2025-12-08 and had been downloaded 18 times. There were no crates depending on this crate on crates.io. 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-6v2j-vr4h-f632 in your dependencies?

O3 Security finds GHSA-6v2j-vr4h-f632 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-6v2j-vr4h-f632: finch_cli_rust | O3 Security