How severe is GHSA-99j7-fhr2-xfj4?

No CVSS score has been assigned to GHSA-99j7-fhr2-xfj4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-99j7-fhr2-xfj4?

GHSA-99j7-fhr2-xfj4 affects the following packages: exploration (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-99j7-fhr2-xfj4?

No patched version of exploration has shipped for GHSA-99j7-fhr2-xfj4 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-99j7-fhr2-xfj4 in my crates.io dependencies?

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

How do I mitigate GHSA-99j7-fhr2-xfj4 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-99j7-fhr2-xfj4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-99j7-fhr2-xfj4 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-99j7-fhr2-xfj4 published, and has it been updated?

GHSA-99j7-fhr2-xfj4 was published on July 10, 2026 and was last updated on July 11, 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

`exploration` was removed from crates.io for malicious codeGHSA-99j7-fhr2-xfj4

GHSA-99j7-fhr2-xfj4 is a security vulnerability in exploration. No vendor fix is recorded yet; mitigation options are listed below.

Also known asRUSTSEC-2026-0155

Published

Jul 10, 2026

Updated

Jul 11, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Jul 11, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀exploration

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

A method within the exploration crate attempted to download and execute a payload from a remote site.

The malicious crate had 1 version published on 2026-06-02, approximately 1 hour before removal, and had no evidence of actual usage. This crate had no dependencies on crates.io.

Rustsec to Kirill Boychenko from the Socket Threat Research Team for reporting this crate.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`exploration`	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 exploration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of exploration has shipped for GHSA-99j7-fhr2-xfj4 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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

A method within the `exploration` crate attempted to download and execute a payload from a remote site. The malicious crate had 1 version published on 2026-06-02, approximately 1 hour before removal, and had no evidence of actual usage. This crate had no dependencies on crates.io. Rustsec to Kirill Boychenko from the [Socket Threat Research Team](https://socket.dev/) for reporting this crate.

O3 Security · Impact-Aware SCA

Is GHSA-99j7-fhr2-xfj4 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works