How severe is GHSA-h5j3-crg5-8jqm?

No CVSS score has been assigned to GHSA-h5j3-crg5-8jqm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h5j3-crg5-8jqm?

GHSA-h5j3-crg5-8jqm affects the following packages: orx-pinned-vec (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-h5j3-crg5-8jqm?

Update orx-pinned-vec to 3.21.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5j3-crg5-8jqm is resolved across your whole dependency graph.

How do I detect GHSA-h5j3-crg5-8jqm in my crates.io dependencies?

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

How do I mitigate GHSA-h5j3-crg5-8jqm 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-h5j3-crg5-8jqm?

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

Is GHSA-h5j3-crg5-8jqm actively exploited in the wild?

No public exploit code has been indexed for GHSA-h5j3-crg5-8jqm 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-h5j3-crg5-8jqm published, and has it been updated?

GHSA-h5j3-crg5-8jqm was published on October 21, 2025 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-h5j3-crg5-8jqm — orx-pinned-vec

Fix: orxfun/orx-pinned-vec#53

GHSA-h5j3-crg5-8jqm is a security vulnerability in orx-pinned-vec. A fix is available for orx-pinned-vec — see the affected versions and patch details below.

orx-pinned-vec has undefined behavior in index_of_ptr with empty slices

Also known asRUSTSEC-2025-0106

Published

Oct 21, 2025

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

🦀orx-pinned-vec

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

The safe function index_of_ptr causes undefined behavior when called with an empty slice.

The issue occurs in the line ptr.add(slice.len() - 1) which underflows when slice.len() is 0, creating a pointer with a massive offset. According to Rust's safety rules, creating such a pointer causes immediate undefined behavior.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`orx-pinned-vec`	all versions	3.21.0`cargo update -p orx-pinned-vec --precise 3.21.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for orx-pinned-vec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update orx-pinned-vec to 3.21.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5j3-crg5-8jqm 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-h5j3-crg5-8jqm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-h5j3-crg5-8jqm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The safe function `index_of_ptr` causes undefined behavior when called with an empty slice. The issue occurs in the line `ptr.add(slice.len() - 1)` which underflows when `slice.len()` is 0, creating a pointer with a massive offset. According to Rust's safety rules, creating such a pointer causes immediate undefined behavior.

O3 Security · Impact-Aware SCA

Is GHSA-h5j3-crg5-8jqm in your dependencies?

O3 Security finds GHSA-h5j3-crg5-8jqm 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