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

GHSA-p5vf-5754-x7p3 polymarket-client-sdks

GHSA-p5vf-5754-x7p3 is a security vulnerability in polymarket-client-sdks. No vendor fix is recorded yet; mitigation options are listed below.

`polymarket-client-sdks` was removed from crates.io for malicious code

Also known asRUSTSEC-2026-0011
Published
Feb 13, 2026
Updated
Feb 14, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Feb 14, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀polymarket-client-sdks

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

It appeared to be typosquatting existing crate polymarket-client-sdk (sdks vs sdk) and attempting to steal credentials from local files.

The malicious crate had 1 version published on 2026-02-09 and had been downloaded only 33 times. There were no crates depending on this crate on crates.io.

Thanks to Roland Peelen for finding and reporting this to the crates.io team!

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🦀crates.iopolymarket-client-sdksall 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 polymarket-client-sdks, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of polymarket-client-sdks has shipped for GHSA-p5vf-5754-x7p3 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-p5vf-5754-x7p3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-p5vf-5754-x7p3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

It appeared to be typosquatting existing crate [`polymarket-client-sdk`](https://crates.io/crates/polymarket-client-sdk) (`sdks` vs `sdk`) and attempting to steal credentials from local files. The malicious crate had 1 version published on 2026-02-09 and had been downloaded only 33 times. There were no crates depending on this crate on crates.io. Thanks to Roland Peelen for finding and reporting this to the crates.io team!
O3 Security · Impact-Aware SCA

Is GHSA-p5vf-5754-x7p3 in your dependencies?

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

GHSA-p5vf-5754-x7p3: polymarket-client-sdks | O3 Security