CVE-2026-40192: Pillow is vulnerable to a FITS GZIP decompression bomb
Pillow is a Python imaging library. Versions 10.3.0 through 12.1.1 did not limit the amount of GZIP-compressed data read when decoding a FITS image, making them vulnerable to decompression bomb attacks. A specially crafted FITS file could cause unbounded memory consumption, leading to denial of service (OOM crash or severe performance degradation). If users are unable to immediately upgrade, they should only open specific image formats, excluding FITS, as a workaround.
Security readout for executives and security teams
Plain-English summary
Pillow can be forced to consume excessive memory when it opens a specially crafted GZIP-compressed FITS image. The practical impact is denial of service: an application, worker, or host processing the image may crash or slow severely. The issue affects Pillow 10.3.0 through 12.1.1 and is addressed in 12.2.0.
Executive priority
Treat as a high-priority availability risk for services processing external images. Prioritize internet-facing upload and media-processing systems first, then internal batch pipelines. There is no source-backed evidence of active exploitation in the provided bundle.
Technical view
The FITS decoder in affected Pillow versions did not limit GZIP-compressed data read during image decoding. This enables a decompression bomb condition causing unbounded memory consumption. The CVE is rated high, CVSS 4.0 score 8.7, with CWE-400, CWE-409, and CWE-770 mappings.
Likely exposure
Exposure is most likely in Python applications, services, or batch pipelines using Pillow 10.3.0 through 12.1.1 to process untrusted or externally supplied image files, especially where FITS is accepted or not explicitly blocked.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The described attack requires a crafted FITS file reaching Pillow’s FITS decoding path. Impact is availability only in the provided CVSS vector.
Researcher notes
Focus validation on Pillow FITS handling and dependency reachability, not just package presence. The public PR, commit, and 12.2.0 release note identify the fix area. Avoid assuming other image formats are affected unless vendor sources expand scope.
Mitigation direction
Upgrade Pillow to version 12.2.0 or later.
Apply relevant downstream vendor updates, including Red Hat errata where applicable.
If upgrade is delayed, allow only required image formats and exclude FITS.
Review upload, conversion, and thumbnailing paths that process user-supplied images.
Monitor Pillow and OS vendor advisories for any revised guidance.
Validation and detection
Inventory direct and transitive Pillow dependencies across applications and containers.
Confirm no deployed environment runs Pillow >=10.3.0 and <12.2.0.
Check whether image-processing flows accept FITS files from untrusted sources.
Verify package updates through lockfiles, images, SBOMs, or runtime dependency reports.
For Red Hat systems, map installed packages to the referenced errata or VEX status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Handling of Highly Compressed Data (Data Amplification)
Improper Handling of Highly Compressed Data (Data Amplification) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.