How severe is GHSA-x468-phr8-h3p3?

No CVSS score has been assigned to GHSA-x468-phr8-h3p3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x468-phr8-h3p3?

GHSA-x468-phr8-h3p3 affects the following packages: uniswap-utils (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-x468-phr8-h3p3?

The records we use list no patched version of uniswap-utils for GHSA-x468-phr8-h3p3. 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-x468-phr8-h3p3 in my crates.io dependencies?

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

How do I mitigate GHSA-x468-phr8-h3p3 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-x468-phr8-h3p3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-x468-phr8-h3p3 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-x468-phr8-h3p3 published, and has it been updated?

GHSA-x468-phr8-h3p3 was published on February 6, 2026 and was last updated on February 23, 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

`uniswap-utils` was removed from crates.io for malicious codeGHSA-x468-phr8-h3p3

GHSA-x468-phr8-h3p3 is a security vulnerability in uniswap-utils. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0145

Published

Feb 6, 2026

Updated

Feb 23, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🦀uniswap-utils

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 depended on the evm-units crate, which appeared to be attempting to steal cryptocurrency.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`uniswap-utils`	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 uniswap-utils, 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 uniswap-utils for GHSA-x468-phr8-h3p3. 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 depended on the `evm-units` crate, which appeared to be attempting to steal cryptocurrency.

O3 Security · Impact-Aware SCA

Is GHSA-x468-phr8-h3p3 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works