CVE-2026-96644 python-pillow CVE debrief

Who should care

Defenders responsible for Windows environments where Pillow is used, especially those handling image processing or using Pillow in their applications, should assess exposure and prioritize updating to version 13.0.0 or later.

Why it matters

The vulnerability in Pillow's WMF/EMF rendering on Windows builds can lead to a heap over-read, potentially disclosing sensitive information. Defenders should prioritize verifying exposure, updating to version 13.0.0 or later, and monitoring image processing workflows for potential malicious activity.

• Potential heap over-read leading to information disclosure
• Verification of Pillow version and exposure in Windows environments is crucial
• Updating to version 13.0.0 or later is necessary to address the vulnerability

Technical summary

The vulnerability exists in Pillow's handling of WMF/EMF images on Windows. The code stores image dimensions without checks and passes them to the native `drawwmf` handler. The handler truncates dimensions to 16-bit for allocation but uses 32-bit values for copying, potentially leading to a heap over-read. This issue affects Pillow versions prior to 13.0.0 on Windows builds, and defenders should prioritize verifying exposure, updating to version 13.0.0 or later, and monitoring image processing workflows for potential malicious activity.

Defensive priority

Defenders should prioritize verifying and updating Pillow to version 13.0.0 or later, especially in Windows environments where the vulnerability is exploited. They should also review and monitor image processing workflows for potential malicious metafiles.

Recommended defensive actions

• Verify and update Pillow to version 13.0.0 or later
• Review and monitor image processing workflows for potential malicious metafiles
• Implement additional security measures for Windows environments where Pillow is used
• Track exceptions and retest remediated assets
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in Pillow versions prior to 13.0.0 on Windows builds. The issue is caused by the lack of range checks on image dimensions and the discrepancy between 16-bit and 32-bit dimension handling in the native `drawwmf` handler.

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.