How severe is GHSA-v935-pqmr-g8v9?

No CVSS score has been assigned to GHSA-v935-pqmr-g8v9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v935-pqmr-g8v9?

GHSA-v935-pqmr-g8v9 affects the following packages: num-bigint (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-v935-pqmr-g8v9?

Update num-bigint to 0.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v935-pqmr-g8v9 is resolved across your whole dependency graph.

How do I detect GHSA-v935-pqmr-g8v9 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for num-bigint. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-v935-pqmr-g8v9 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-v935-pqmr-g8v9?

O3 pinpoints whether GHSA-v935-pqmr-g8v9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-v935-pqmr-g8v9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v935-pqmr-g8v9 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-v935-pqmr-g8v9 published, and has it been updated?

GHSA-v935-pqmr-g8v9 was published on November 3, 2021 and was last updated on November 3, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-v935-pqmr-g8v9: Unexpected panics in num-bigint

Blast Radius

1 pkg affected

🦀num-bigint

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

Impact

Two scenarios were reported where BigInt and BigUint multiplication may unexpectedly panic.

The internal mac3 function did not expect the possibility of non-empty all-zero inputs, leading to an unwrap() panic.
A buffer was allocated with less capacity than needed for an intermediate result, leading to an assertion panic.

Rust panics can either cause stack unwinding or program abort, depending on the application configuration. In some settings, an unexpected panic may constitute a denial-of-service vulnerability.

Patches

Both problems were introduced in version 0.4.1, and are fixed in version 0.4.3.

For more information

If you have any questions or comments about this advisory, please open an issue in the num-bigint repo.

Acknowledgements

Thanks to Guido Vranken and Arvid Norberg for privately reporting these issues to the author.

References

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`num-bigint`	≥ 0.4.1&&< 0.4.3	0.4.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for num-bigint. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update num-bigint to 0.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v935-pqmr-g8v9 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 pinpoints whether GHSA-v935-pqmr-g8v9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v935-pqmr-g8v9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Two scenarios were reported where `BigInt` and `BigUint` multiplication may unexpectedly panic. - The internal `mac3` function did not expect the possibility of non-empty all-zero inputs, leading to an `unwrap()` panic. - A buffer was allocated with less capacity than needed for an intermediate result, leading to an assertion panic. Rust panics can either cause stack unwinding or program abort, depending on the application configuration. In some settings, an unexpected panic may constitute a denial-of-service vulnerability. ### Patches Both problems were introduced in version 0.

O3 Security · Impact-Aware SCA

Is GHSA-v935-pqmr-g8v9 in your dependencies?

O3 detects GHSA-v935-pqmr-g8v9 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works