Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Unexpected panics in num-bigint

GHSA-v935-pqmr-g8v9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (num-bigint 0.4.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io num-bigint

    Affected
    >= 0.4.1, < 0.4.3
    Fixed in
    0.4.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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 GHSA-v935-pqmr-g8v9 num-bigint#228

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-v935-pqmr-g8v9

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-v935-pqmr-g8v9

Advisory: Unexpected panics in num-bigint
IDs: GHSA-v935-pqmr-g8v9
Record: https://patchnext.com/advisories/ghsa-v935-pqmr-g8v9 (revision 1, source checked 26 Oct 2026, 15:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: num-bigint 0.4.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io num-bigint: affected >= 0.4.1, < 0.4.3; fixed in 0.4.3

## Suggested inspection (read-only)
- crates.io num-bigint: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on num-bigint.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v935-pqmr-g8v9 (GitHub-reviewed advisory GHSA-v935-pqmr-g8v9 lists affected ranges: crates.io num-bigint >=0.4.1 <0.4.3)

Commands are suggestions: review each one before running it.

Loading voting…