Process crash via unchecked JPEG comment write
Published Oct 21, 2026 · Updated Oct 21, 2026
Heap overflow in Pillow's JPEG encoder 9.4.0 through 12.3.0 allows attackers to crash processes via crafted image metadata. ImagingJpegEncode() writes a comment after an ICC profile exhausts the output buffer, wrapping libjpeg's free-space counter and overwriting adjacent heap memory. Applications must re-save untrusted images as JPEG while preserving the profile and forwarded comment; the public reproducer demonstrates a crash, while code execution remains unproven.
Summary
What happened
Heap overflow in Pillow's JPEG encoder 9.4.0 through 12.3.0 allows attackers to crash processes via crafted image metadata. ImagingJpegEncode() writes a comment after an ICC profile exhausts the output buffer, wrapping libjpeg's free-space counter and overwriting adjacent heap memory. Applications must re-save untrusted images as JPEG while preserving the profile and forwarded comment; the public reproducer demonstrates a crash, while code execution remains unproven.
The record
- CVE
- CVE-2026-96778
- Published
- Oct 21, 2026
- Updated
- Oct 21, 2026
- Vendor
- Python Pillow
- Product
- Pillow
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 21, 2026CVE publishedPublication date reported by the CVE source.
- Oct 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 9.4.0, < 13.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- Upstream JPEG comment overflow reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us