GHSA-p4m5-32pr-2hqr — pypop-genomics
Fix: alexlancaster/pypop@2e5c495GHSA-p4m5-32pr-2hqr is a security vulnerability in pypop-genomics. A fix is available for pypop-genomics — see the affected versions and patch details below.
PyPop C extensions possible vulnerability: missing arguments and redundant null pointers
Real-World Exposure
pypop-genomicsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Code scanning revealed possible vulnerability in C extensions for PyPop: incorrect function calls (missing arguments or wrongly typed arguments) and redundant null pointers.
Patches
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
Workarounds
No. Upgrade to the latest package: 1.0.2.
References
N/A
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | pypop-genomics | all versions | 1.0.2pip install --upgrade 'pypop-genomics==1.0.2' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pypop-genomics, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pypop-genomics to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p4m5-32pr-2hqr 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p4m5-32pr-2hqr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-p4m5-32pr-2hqr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p4m5-32pr-2hqr in your dependencies?
O3 Security finds GHSA-p4m5-32pr-2hqr across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.