# CVE-2026-111275: nifti_clib through 3.0.1 Stack Out-of-Bounds Access via nifti_convert_n2hdr2nim

> Attackers can cause stack memory corruption or crashes in applications using nifti_clib by supplying a crafted NIfTI-2 header file.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-jj37-jg79-p9qw, UBUNTU-CVE-2026-111275

## What is CVE-2026-111275?

CVE-2026-111275 is a medium-severity memory corruption vulnerability in NIFTI-Imaging nifti_clib, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

nifti_clib through 3.0.1 contains a stack-based out-of-bounds read and write vulnerability in nifti_convert_n2hdr2nim() because the NIfTI-2 dim[0] value is never range-checked. Attackers can supply a crafted 540-byte NIfTI-2 header read via nifti_image_read() to crash applications or corrupt stack memory.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-111275 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111275 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111275 is a medium-severity memory corruption vulnerability in NIFTI-Imaging nifti_clib, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111275 exists.

Affected product: NIFTI-Imaging nifti_clib. 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-111275/ (Markdown: https://insights.sbomify.com/CVE-2026-111275/index.md)
```

## Sources

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

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