# CVE-2026-118590: nipy nibabel Header volumeutils.py array_from_file memory allocation


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-118590, GHSA-5v4h-cwmw-rr9x, UBUNTU-CVE-2026-118590

## What is CVE-2026-118590?

CVE-2026-118590 is a medium-severity vulnerability in nipy nibabel, published on 29 Oct 2026. 

### Official description

A security vulnerability has been detected in nipy nibabel up to 5.4.2. The affected element is the function array_from_file of the file nibabel/volumeutils.py of the component Header Handler. The manipulation leads to uncontrolled memory allocation. The attack is possible to be carried out remotely. The pull request to fix this issue awaits acceptance.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-118590?


## How do I fix CVE-2026-118590?

No fix has been published for CVE-2026-118590 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118590 being exploited?

There is no known exploitation of CVE-2026-118590 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118590 and fix it if it is affected.

What it is: CVE-2026-118590 is a medium-severity vulnerability in nipy nibabel, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118590 in the wild and no public exploit code.

Affected product: nipy nibabel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118590/ (Markdown: https://insights.sbomify.com/CVE-2026-118590/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118590
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118590
- OSV: https://osv.dev/vulnerability/CVE-2026-118590

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118590/
Summaries are generated and may contain mistakes; the official description above is the record.