Which versions of pypop-genomics are affected by GHSA-P4M5-32PR-2HQR?

pypop-genomics (pip) versions < 1.0.2 is affected.

Is there a fix for GHSA-P4M5-32PR-2HQR?

Yes. GHSA-P4M5-32PR-2HQR is fixed in 1.0.2. Upgrade to this version or later.

Is GHSA-P4M5-32PR-2HQR exploitable, and should I be worried?

Whether GHSA-P4M5-32PR-2HQR 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-P4M5-32PR-2HQR 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-P4M5-32PR-2HQR?

Upgrade pypop-genomics to 1.0.2 or later.

GHSA-P4M5-32PR-2HQR in pypop-genomics

Q: What is GHSA-P4M5-32PR-2HQR?

GHSA-P4M5-32PR-2HQR is a low-severity security vulnerability in pypop-genomics (pip), affecting versions < 1.0.2. It is fixed in 1.0.2.

Q: Is there a fix for GHSA-P4M5-32PR-2HQR?

Yes. GHSA-P4M5-32PR-2HQR is fixed in 1.0.2. Upgrade to this version or later.

Q: Is GHSA-P4M5-32PR-2HQR exploitable, and should I be worried?

Whether GHSA-P4M5-32PR-2HQR 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-P4M5-32PR-2HQR 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-P4M5-32PR-2HQR?

Upgrade pypop-genomics to 1.0.2 or later.

GHSA-P4M5-32PR-2HQR

GHSA-P4M5-32PR-2HQR is a low-severity security vulnerability in pypop-genomics (pip), affecting versions < 1.0.2. It is fixed in 1.0.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

PyPop C extensions possible vulnerability: missing arguments and redundant null pointers

Workarounds

No. Upgrade to the latest package: 1.0.2.

References

N/A

Impact

Code scanning revealed possible vulnerability in C extensions for PyPop: incorrect function calls (missing arguments or wrongly typed arguments) and redundant null pointers.

Affected versions

pypop-genomics (< 1.0.2)

Security releases

pypop-genomics → 1.0.2 (pip)

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

The problem has been patched and fixed in the latest release of PyPop: 1.0.2. Please upgrade your PyPop installation via:

pip install -U pypop-genomics

Frequently Asked Questions

What is GHSA-P4M5-32PR-2HQR? GHSA-P4M5-32PR-2HQR is a low-severity security vulnerability in pypop-genomics (pip), affecting versions < 1.0.2. It is fixed in 1.0.2.
Which versions of pypop-genomics are affected by GHSA-P4M5-32PR-2HQR? pypop-genomics (pip) versions < 1.0.2 is affected.
Is there a fix for GHSA-P4M5-32PR-2HQR? Yes. GHSA-P4M5-32PR-2HQR is fixed in 1.0.2. Upgrade to this version or later.
Is GHSA-P4M5-32PR-2HQR exploitable, and should I be worried? Whether GHSA-P4M5-32PR-2HQR 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-P4M5-32PR-2HQR 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-P4M5-32PR-2HQR? Upgrade pypop-genomics to 1.0.2 or later.