External risk intelligence

Pillow JPEG Decoder Heap Corruption Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-112403

Pillow is a widely used third-party software library integrated into many applications. While it is often used to process user-supplied images in web applications, which can be internet-facing, the library itself is not a standalone service or public-facing endpoint. Its reachability depends entirely on how an individual developer implements image processing within their specific application architecture.

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in a popular Python imaging library, Pillow. This issue, related to how it processes certain JPEG images, could lead to memory corruption, application crashes, or even the execution of unauthorized code if an attacker supplies a specially crafted image. The main concern is confirming if our applications utilize this library for image processing, as its exposure is dependent on specific implementation.

Image processing vulnerability in a Python library.
Affects applications processing crafted JPEG images.
Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could target applications that use Pillow to process JPEG images. If an application uses Pillow's image scaling or thumbnailing features with a specially crafted JPEG, the library's JPEG decoder might not correctly handle the image dimensions. This could lead to memory corruption, potentially allowing an attacker to crash the application or execute arbitrary code.

Requires attacker-controlled JPEG input.
Triggered by image scaling or thumbnailing.
Corrupts memory, may allow code execution.

Live Threat

Current exploitation, exposure, and threat context

When processing specially crafted JPEG images, Pillow's JPEG decoder, when linked with specific versions of libjpeg-turbo, may incorrectly write data, potentially corrupting memory, causing a denial of service, or allowing for code execution. This could impact applications that use Pillow's `draft()` or `thumbnail()` functions to downscale images.

Heap memory corruption or process crash.
Malicious JPEG processed via downscaling function.
Potential for arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and infrastructure teams are likely responsible for addressing this vulnerability. The first practical step is to identify all systems processing JPEG images using this library, determine their business criticality and network exposure, and locate the accountable owner. Remediation planning should then be prioritized based on this risk assessment.

Identify accountable application owners.
Verify JPEG processing exposure.
Plan risk-based remediation.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Pillow?

Pillow is a prominent open-source library for the Python programming language used to open, manipulate, and save many different image file formats. Developers frequently integrate it into applications to handle tasks like resizing, rotating, or converting images. Because it supports a vast array of file types and complex decoding operations, it is a foundational tool for websites and services that process user-uploaded content.

What is the vulnerability in CVE-2026-112403?

This flaw is a heap-based buffer overflow, classified as CWE-122. It occurs because the library’s JPEG decoder fails to properly verify the actual image dimensions after scaling. When the library attempts to write processed image data into memory, it may use an incorrect buffer size, causing data to spill into adjacent memory. This corruption can crash the application or, in certain scenarios, allow an attacker to gain unauthorized control over the process.

How is this vulnerability triggered?

An attacker must supply a specifically crafted 8-bit lossless SOF3 JPEG to an application that processes the image using Pillow's `draft()` or `thumbnail()` functions. The bug specifically affects builds linked with libjpeg-turbo 3.x, which may ignore requested scaling dimensions. Note that simply viewing a standard JPEG does not trigger this; the application must explicitly perform downscaling operations on a malicious file formatted to exploit this mismatch.

Is my application at risk according to Halo Surface Signal?

Pillow is a library, not a standalone service, so your risk depends on your application's architecture. Halo Surface Signal notes that while Pillow is often used in internet-facing web apps to process user-supplied images, its reachability is unique to your setup. You must determine if your specific code accepts user-provided JPEGs and passes them through the affected scaling functions, as the library itself is only vulnerable when integrated into an active processing workflow.

How should I respond if my application uses Pillow?

Your first step is to inventory all applications that use the library to process JPEG images and confirm if they use version 13.0.0 or older. Once you have identified the systems, determine which ones handle input from untrusted sources or the internet. Prioritize updating the Pillow library to version 13.0.0, which includes the fix, and coordinate with the respective application owners to schedule testing and deployment of the update.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.