What is GHSA-V935-PQMR-G8V9?

GHSA-V935-PQMR-G8V9 is a medium-severity improper input validation vulnerability in num-bigint (rust), affecting versions >= 0.4.1, < 0.4.3. It is fixed in 0.4.3. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

Which versions of num-bigint are affected by GHSA-V935-PQMR-G8V9?

num-bigint (rust) versions >= 0.4.1, < 0.4.3 is affected.

Is there a fix for GHSA-V935-PQMR-G8V9?

Yes. GHSA-V935-PQMR-G8V9 is fixed in 0.4.3. Upgrade to this version or later.

Is GHSA-V935-PQMR-G8V9 exploitable, and should I be worried?

Whether GHSA-V935-PQMR-G8V9 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-V935-PQMR-G8V9 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-V935-PQMR-G8V9?

Upgrade num-bigint to 0.4.3 or later.

GHSA-V935-PQMR-G8V9 in num-bigint

Q: Which versions of num-bigint are affected by GHSA-V935-PQMR-G8V9?

num-bigint (rust) versions >= 0.4.1, < 0.4.3 is affected.

Q: Is there a fix for GHSA-V935-PQMR-G8V9?

Yes. GHSA-V935-PQMR-G8V9 is fixed in 0.4.3. Upgrade to this version or later.

Q: Is GHSA-V935-PQMR-G8V9 exploitable, and should I be worried?

Whether GHSA-V935-PQMR-G8V9 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-V935-PQMR-G8V9 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-V935-PQMR-G8V9?

Upgrade num-bigint to 0.4.3 or later.

Summary

Unexpected panics in num-bigint

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

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

Affected versions

num-bigint (>= 0.4.1, < 0.4.3)

Security releases

num-bigint → 0.4.3 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is GHSA-V935-PQMR-G8V9? GHSA-V935-PQMR-G8V9 is a medium-severity improper input validation vulnerability in num-bigint (rust), affecting versions >= 0.4.1, < 0.4.3. It is fixed in 0.4.3. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
Which versions of num-bigint are affected by GHSA-V935-PQMR-G8V9? num-bigint (rust) versions >= 0.4.1, < 0.4.3 is affected.
Is there a fix for GHSA-V935-PQMR-G8V9? Yes. GHSA-V935-PQMR-G8V9 is fixed in 0.4.3. Upgrade to this version or later.
Is GHSA-V935-PQMR-G8V9 exploitable, and should I be worried? Whether GHSA-V935-PQMR-G8V9 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-V935-PQMR-G8V9 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-V935-PQMR-G8V9? Upgrade num-bigint to 0.4.3 or later.