How severe is GHSA-p5vf-5754-x7p3?

No CVSS score has been assigned to GHSA-p5vf-5754-x7p3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p5vf-5754-x7p3?

GHSA-p5vf-5754-x7p3 affects the following packages: polymarket-client-sdks (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-p5vf-5754-x7p3?

The records we use list no patched version of polymarket-client-sdks for GHSA-p5vf-5754-x7p3. 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-p5vf-5754-x7p3 in my crates.io dependencies?

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.

How do I mitigate GHSA-p5vf-5754-x7p3 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-p5vf-5754-x7p3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p5vf-5754-x7p3 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-p5vf-5754-x7p3 published, and has it been updated?

GHSA-p5vf-5754-x7p3 was published on February 13, 2026 and was last updated on February 14, 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

`polymarket-client-sdks` was removed from crates.io for malicious codeGHSA-p5vf-5754-x7p3

GHSA-p5vf-5754-x7p3 is a security vulnerability in polymarket-client-sdks. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

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

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`polymarket-client-sdks`	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 polymarket-client-sdks, 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 polymarket-client-sdks for GHSA-p5vf-5754-x7p3. 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

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?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works