cve.bz

CVE-2026-118590 nipy nibabel: Uncontrolled Resource Consumption

6.9 mediumEPSS 0.4%

Medium (6.9) in nipy nibabel. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.9 medium
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

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-789 Memory Allocation with Excessive Size Value
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-118590 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118590?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118590?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118590 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nipy nibabel5.4.0
nipy nibabel5.4.1
nipy nibabel5.4.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14nibabelno fix listedDEBIAN-CVE-2026-118590
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morenipy, nibabelno fix listedUBUNTU-CVE-2026-118590
openSUSETumbleweedpython-nibabel5.5.0-1.1openSUSE-SU-2026:12557-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity for Red Hat because exploitation is limited to a denial of service through memory exhaustion, requiring an application to parse an untrusted or maliciously crafted neuroimaging file. While excessive memory consumption can terminate the processing application or cause resource starvation on the host, the flaw does not allow remote code execution or unauthorized data modification. Furthermore, nibabel is a specialized scientific library not deployed as part of core enterprise services, confining the blast radius to workflows that ingest unvalidated user files.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-118590.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON