CVE-2026-111275 NIFTI-Imaging CVE debrief

Who should care

Defenders responsible for systems or applications using the nifti_clib library, especially those handling NIfTI-2 headers from untrusted sources, should assess exposure and prioritize verification and potential updates.

Why it matters

CVE-2026-111275 is a stack-based out-of-bounds read and write vulnerability in nifti_clib through 3.0.1. Defenders should prioritize verifying the vulnerability, assessing exposure in applications using this library, and planning for potential updates or mitigations.

• Potential application crashes due to out-of-bounds reads
• Stack memory corruption due to out-of-bounds writes
• Need for verification of affected versions and exposure to untrusted input
• Prioritization of updates or mitigations if vulnerable versions are in use

Technical summary

The nifti_convert_n2hdr2nim() function in nifti_clib through 3.0.1 does not perform range checking on the NIfTI-2 dim[0] value, leading to a stack-based out-of-bounds read and write vulnerability. This can be triggered by a crafted 540-byte NIfTI-2 header. The vulnerability exists due to the lack of input validation on the dim[0] value. Defenders should prioritize verifying the vulnerability in nifti_clib versions up to 3.0.1 and assessing if applications using this library are exposed to untrusted input. Affected systems may experience potential application crashes or stack memory corruption.

Defensive priority

Defenders should prioritize verifying the vulnerability in nifti_clib versions up to 3.0.1 and assessing if applications using this library are exposed to untrusted input.

Recommended defensive actions

• Verify the vulnerability in nifti_clib versions up to 3.0.1
• Assess if applications using this library are exposed to untrusted input
• Consider updating to a fixed version if available
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the actual impact and affected versions require further verification from the official sources. The vulnerability exists in nifti_clib through 3.0.1. The lack of range checking on the NIfTI-2 dim[0] value can be exploited. The CVE Program record and NVD detail page offer source-provided metadata and vulnerability assessments. However, defenders must verify the vulnerability's impact and assess exposure in their specific environments. Official advisories and CVE/CV2

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.