How severe is GHSA-9fjq-45qv-pcm7?

No CVSS score has been assigned to GHSA-9fjq-45qv-pcm7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9fjq-45qv-pcm7?

GHSA-9fjq-45qv-pcm7 affects the following packages: ruint (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-9fjq-45qv-pcm7?

The records we use list no patched version of ruint for GHSA-9fjq-45qv-pcm7. 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-9fjq-45qv-pcm7 in my crates.io dependencies?

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

How do I mitigate GHSA-9fjq-45qv-pcm7 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-9fjq-45qv-pcm7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9fjq-45qv-pcm7 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-9fjq-45qv-pcm7 published, and has it been updated?

GHSA-9fjq-45qv-pcm7 was published on December 26, 2025 and was last updated on December 27, 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

ruint affected by unsoundness of safe `reciprocal_mg10`GHSA-9fjq-45qv-pcm7

GHSA-9fjq-45qv-pcm7 is a remote code execution vulnerability in ruint. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0137

Published

Dec 26, 2025

Updated

Dec 27, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Dec 27, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀ruint

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 function reciprocal_mg10 is marked as safe but can trigger undefined behavior (out-of-bounds access) because it relies on debug_assert! for safety checks instead of assert!.

When compiled in release mode, the debug_assert! is optimized out, potentially allowing invalid inputs to cause memory corruption.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ruint`	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 ruint, 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 ruint for GHSA-9fjq-45qv-pcm7. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

The function `reciprocal_mg10` is marked as safe but can trigger undefined behavior (out-of-bounds access) because it relies on `debug_assert!` for safety checks instead of `assert!`. When compiled in release mode, the `debug_assert!` is optimized out, potentially allowing invalid inputs to cause memory corruption.

O3 Security · Impact-Aware SCA

Is GHSA-9fjq-45qv-pcm7 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works