NumPy NULL Pointer DereferenceGHSA-5545-2q6w-2gh6
HIGHGHSA-5545-2q6w-2gh6 is a high-severity (CVSS 7.5) NULL Pointer Dereference vulnerability in numpy. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for numpy — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
numpyReal-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
Null Pointer Dereference vulnerability exists in numpy.sort in NumPy < and 1.19 in the PyArray_DescrNew function due to missing return-value validation, which allows attackers to conduct DoS attacks by repetitively creating sort arrays. NOTE: While correct that validation is missing, an error can only occur due to an exhaustion of memory. If the user can exhaust memory, they are already privileged. Further, it should be practically impossible to construct an attack which can target the memory exhaustion to occur at exactly this place
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | numpy | all versions | 1.19pip install --upgrade 'numpy==1.19' |
Affected Products
numpynumpyResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for numpy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update numpy to 1.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5545-2q6w-2gh6 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenStack Platform 16.1 | numpy-1:1.17.0-11.el8ost | RHSA-2022:8861 |
| Red Hat OpenStack Platform 16.2 | numpy-1:1.17.0-11.el8ost | RHSA-2022:8852 |
Frequently Asked Questions
Is GHSA-5545-2q6w-2gh6 in your dependencies?
Find it across PyPI, including transitive dependencies.