Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

Pillow: GIF seek keeps rejected size after DecompressionBombError, allowing DoS

CVE-2026-112400GHSA-65qm-jvmh-6pqg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pillow 13.0.0; pillow 13.0.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Bitnami pillow

    Affected
    >= 9.2.0, < 13.0.0
    Fixed in
    13.0.0

  • PyPI pillow

    Affected
    >= 9.2.0, < 13.0.0
    Fixed in
    13.0.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-112400: 0.59% estimated exploitation activity in the next 30 days; percentile 48.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

``` ============================================================================ GIF seek keeps rejected size after DecompressionBombError, allowing DoS Location: src/PIL/GifImagePlugin.py:293 in GifImageFile._seek() Commit: a707c6b21c313880d0771e54965d142dd42358b6 ============================================================================ ``` A GIF of about 60 bytes can make Pillow allocate gigabytes of memory. This affects applications that catch the "image too large" error raised while stepping to a later animation frame and then keep using the same image object. Pillow correctly refuses the oversized frame, but it stores the refused dimensions on the image object anyway, and later operations size their memory from them. An attacker who can upload a GIF to such a service can exhaust its memory: the process either fails with an out-of-memory error after committing gigabytes, or is killed by the operating system. There is no memory corruption. The bug is in `GifImageFile._seek()`…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 7 · amended ·

    Amended from osv record BIT-pillow-2026-112400

  2. Revision 6 · amended ·

    Amended from ghsa record GHSA-65qm-jvmh-6pqg

  3. Revision 5 · amended ·

    Amended from osv record BIT-pillow-2026-112400

  4. Revision 4 · amended ·

    Amended from osv record GHSA-65qm-jvmh-6pqg

  5. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  6. Revision 2 · amended ·

    Amended from osv record GHSA-65qm-jvmh-6pqg

  7. Revision 1 · created ·

    Published from ghsa record GHSA-65qm-jvmh-6pqg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-112400

Advisory: Pillow: GIF seek keeps rejected size after DecompressionBombError, allowing DoS
IDs: CVE-2026-112400, GHSA-65qm-jvmh-6pqg
Record: https://patchnext.com/advisories/cve-2026-112400 (revision 7, source checked 30 Oct 2026, 07:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pillow 13.0.0; pillow 13.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Bitnami pillow: affected >= 9.2.0, < 13.0.0; fixed in 13.0.0
- PyPI pillow: affected >= 9.2.0, < 13.0.0; fixed in 13.0.0

## Suggested inspection (read-only)
- Bitnami pillow: check the installed version with your package manager.
- `python -m pip show pillow`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pillow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-65qm-jvmh-6pqg (GitHub-reviewed advisory GHSA-65qm-jvmh-6pqg lists affected ranges: PyPI pillow >=9.2.0 <13.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-65qm-jvmh-6pqg (OSV record GHSA-65qm-jvmh-6pqg lists affected ranges: PyPI pillow >=9.2.0 <13.0.0 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-pillow-2026-112400 (OSV record BIT-pillow-2026-112400 lists affected ranges: Bitnami pillow >=9.2.0 <13.0.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…