Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

Pillow: ReDoS in XbmImagePlugin: 512-byte file stalls Image.open() for minutes

CVE-2026-112901GHSA-xgh8-jp6q-p5x8

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
    < 13.0.0
    Fixed in
    13.0.0

  • PyPI pillow

    Affected
    < 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
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-112901: 0.53% estimated exploitation activity in the next 30 days; percentile 44.99 (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.

``` ============================================================================ ReDoS in XbmImagePlugin: 512-byte file stalls Image.open() for minutes Location: src/PIL/XbmImagePlugin.py:58 in XbmImageFile._open() Commit: a707c6b21c313880d0771e54965d142dd42358b6 ============================================================================ ``` A crafted 512-byte file makes Pillow's `Image.open()` spend about six minutes of processor time on one core before it gives up with `UnidentifiedImageError`. Anyone who can hand bytes to an application that opens images with Pillow's default settings can trigger this, for example through an upload form, a thumbnailer, or a service that checks whether a blob is an image. A few such files sent at once can tie up a typical pool of worker processes. The cause is the `xbm_head` regular expression in `src/PIL/XbmImagePlugin.py:32-40`, which `XbmImageFile._open()` (line 58) runs over the first 512 bytes of any stream whose prefix starts with `#define`.…

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

    Amended from osv record BIT-pillow-2026-112901

  2. Revision 9 · amended ·

    Amended from osv record BIT-pillow-2026-112901

  3. Revision 8 · amended ·

    Amended from osv record PYSEC-2026-4335

  4. Revision 7 · amended ·

    Amended from osv record GHSA-xgh8-jp6q-p5x8

  5. Revision 6 · amended ·

    Amended from ghsa record GHSA-xgh8-jp6q-p5x8

  6. Revision 5 · amended ·

    Amended from osv record BIT-pillow-2026-112901

  7. Revision 4 · amended ·

    Amended from osv record GHSA-xgh8-jp6q-p5x8

  8. Revision 3 · amended ·

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

  9. Revision 2 · amended ·

    Amended from osv record GHSA-xgh8-jp6q-p5x8

  10. Revision 1 · created ·

    Published from ghsa record GHSA-xgh8-jp6q-p5x8

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-112901

Advisory: Pillow: ReDoS in XbmImagePlugin: 512-byte file stalls Image.open() for minutes
IDs: CVE-2026-112901, GHSA-xgh8-jp6q-p5x8
Record: https://patchnext.com/advisories/cve-2026-112901 (revision 10, 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: Medium (CVSS 6.9)
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 < 13.0.0; fixed in 13.0.0
- PyPI pillow: affected < 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-xgh8-jp6q-p5x8 (GitHub-reviewed advisory GHSA-xgh8-jp6q-p5x8 lists affected ranges: PyPI pillow >=0 <=12.3.0)
- Verified: https://osv.dev/vulnerability/GHSA-xgh8-jp6q-p5x8 (OSV record GHSA-xgh8-jp6q-p5x8 lists affected ranges: PyPI pillow >=0 <13.0.0 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-pillow-2026-112901 (OSV record BIT-pillow-2026-112901 lists affected ranges: Bitnami pillow >=0 <13.0.0 (fixed))
- Verified: https://osv.dev/vulnerability/PYSEC-2026-4335 (OSV record PYSEC-2026-4335 lists affected ranges: PyPI pillow >=0 <13.0.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…