How severe is GHSA-f95p-4cv5-8w8x?

No CVSS score has been assigned to GHSA-f95p-4cv5-8w8x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f95p-4cv5-8w8x?

GHSA-f95p-4cv5-8w8x affects the following packages: linkme (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-f95p-4cv5-8w8x?

Update linkme to 0.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f95p-4cv5-8w8x is resolved across your whole dependency graph.

How do I detect GHSA-f95p-4cv5-8w8x in my crates.io dependencies?

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

How do I mitigate GHSA-f95p-4cv5-8w8x 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.

How does O3 Security protect against GHSA-f95p-4cv5-8w8x?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f95p-4cv5-8w8x can be triaged on real exposure rather than presence alone.

Is GHSA-f95p-4cv5-8w8x actively exploited in the wild?

No public exploit code has been indexed for GHSA-f95p-4cv5-8w8x 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-f95p-4cv5-8w8x published, and has it been updated?

GHSA-f95p-4cv5-8w8x was published on December 4, 2024 and was last updated on October 28, 2025. 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

GHSA-f95p-4cv5-8w8x — linkme

GHSA-f95p-4cv5-8w8x is a security vulnerability in linkme. A fix is available for linkme — see the affected versions and patch details below.

linkme fails to ensure slice elements match the slice's declared type

Also known asRUSTSEC-2024-0407

Published

Dec 4, 2024

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀linkme

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

Affected versions allow populating a DistributedSlice of T with elements of an arbitrary other type that coerces to T. For example, elements of type &&str could end up in a slice of type [&str], since &&str coerces to &str via a deref coercion.

The flaw was corrected by implementing typechecking for distributed slice elements in such a way that coercion no longer occurs. The element's type must be a subtype of the slice's declared element type.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`linkme`	all versions	0.3.24`cargo update -p linkme --precise 0.3.24`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for linkme, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update linkme to 0.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f95p-4cv5-8w8x is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f95p-4cv5-8w8x can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f95p-4cv5-8w8x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions allow populating a DistributedSlice of T with elements of an arbitrary other type that coerces to T. For example, elements of type `&&str` could end up in a slice of type `[&str]`, since `&&str` coerces to `&str` via a deref coercion. The flaw was corrected by implementing typechecking for distributed slice elements in such a way that coercion no longer occurs. The element's type must be a subtype of the slice's declared element type.

O3 Security · Impact-Aware SCA

Is GHSA-f95p-4cv5-8w8x in your dependencies?

O3 Security finds GHSA-f95p-4cv5-8w8x across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works