CVE-2026-112404

waiting for further signalsZero needs more public information before it can validate it.

GHSA-c6hw-5grf-ff96 ↗EUVD-2026-104645 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
pip Pillow <= 12.3.0
fixed in 13.0.0
CWE-126 Buffer Over-read
ETK-2026-2130Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/Pillow
1d 03h 37msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal −2.5dcve.org publicationwaiting for further signals+0.4d
−2d
−1d
0

description

Pillow versions before 13.0.0 can read beyond a decode buffer when processing malformed TIFF images with inconsistent image metadata. An attacker who can cause an application to open and load such an image may expose process-memory bytes in decoded output or crash the image-processing process.

mitigation

Upgrade Pillow to version 13.0.0 or later. Until upgraded, prevent untrusted TIFF files from reaching Pillow image-loading workflows.

fixed in 13.0.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.29%20th percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 21:27Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-17 10:35Z
  2. 2026-10-19 21:27Z

this entry in the feed

GET /api/v1/feed/CVE-2026-112404

{
  "etk_id": "ETK-2026-2130",
  "cve_id": "CVE-2026-112404",
  "display_id": "CVE-2026-112404",
  "ghsa_id": "GHSA-c6hw-5grf-ff96",
  "euvd_id": "EUVD-2026-104645",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in Pillow TIFF decoding",
  "summary": "Pillow versions before 13.0.0 can read beyond a decode buffer when processing malformed TIFF images with inconsistent image metadata. An attacker who can cause an application to open and load such an image may expose process-memory bytes in decoded output or crash the image-processing process.",
  "mitigation": "Upgrade Pillow to version 13.0.0 or later. Until upgraded, prevent untrusted TIFF files from reaching Pillow image-loading workflows.",
  "vendor": "pip",
  "product": "Pillow",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 12.3.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "13.0.0"
      ],
      "package_name": "Pillow",
      "purl": "pkg:pypi/Pillow"
    }
  ],
  "cwes": [
    126
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0029,
  "epss_percentile": 0.2041,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.087847166666666,
  "t0_at": "2026-10-19T21:27:56.705000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-17T10:35:54+00:00",
      "days": -2.452809085648148,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T21:27:56.705000+00:00",
      "url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-c6hw-5grf-ff96"
    }
  }
}

published 2026-10-20 07:13Z
last change 2026-10-21 10:15Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.