nipy nibabel up to 5.4.2 Header nibabel/volumeutils.py array_from_file memory allocation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 1.26+ |
Summary
A vulnerability was found in nipy nibabel up to 5.4.2. It has been declared as problematic. The impacted element is the function array_from_file of the file nibabel/volumeutils.py of the component Header Handler. The manipulation results in memory allocation.
This vulnerability was named CVE-2026-118590. The attack may be performed from remote. There is no available exploit.
The pull request to fix this issue awaits acceptance.
Details
A vulnerability was found in nipy nibabel up to 5.4.2. It has been classified as problematic. Affected is the function array_from_file of the file nibabel/volumeutils.py of the component Header Handler. The manipulation with an unknown input leads to a memory allocation vulnerability. CWE is classifying the issue as CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. This is going to have an impact on availability.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-118590. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.
The pull request to fix this issue awaits acceptance.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/nipy/nibabel/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory allocationCWE: CWE-789 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/28/2026 Advisory disclosed10/28/2026 VulDB entry created
10/28/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 1566
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-118590 (🔒)
GCVE (CVE): GCVE-0-2026-118590
GCVE (VulDB): GCVE-100-428028
Entry
Created: 10/28/2026 17:24Changes: 10/28/2026 17:24 (56)
Complete: 🔍
Submitter: Mohammedix88
Cache ID: 216::103
Submit
Accepted
- Submit #1026208: nipy nibabel 5.4.2 Uncontrolled Memory Allocation (by github.com)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.