CVE-2026-112399

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

GHSA-5xm2-6676-qcp9 ↗EUVD-2026-104635 ↗

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.
python-pillow Pillow 8.1.0 - 12.3.0
fixed in 13.0.0
CWE-789 Memory Allocation with Excessive Size Value
ETK-2026-2106Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/Pillow
1d 10h 39msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h02m
0
+2h
+6h
+8h
+10h
+12h

description

Pillow versions 8.1.0 through 12.x can consume excessive memory when opening a specially formed APNG image. An attacker who can cause an application to process an untrusted APNG may deny service by exhausting memory, even if the application only opens the image.

mitigation

Upgrade Pillow to version 13.0.0 or later. Until upgraded, do not process untrusted APNG files in services with limited memory.

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
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 21:10Z
Δ 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-19 21:10Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2106",
  "cve_id": "CVE-2026-112399",
  "display_id": "CVE-2026-112399",
  "ghsa_id": "GHSA-5xm2-6676-qcp9",
  "euvd_id": "EUVD-2026-104635",
  "status": "published",
  "anchor_state": "anchored",
  "title": "APNG memory exhaustion in Pillow",
  "summary": "Pillow versions 8.1.0 through 12.x can consume excessive memory when opening a specially formed APNG image. An attacker who can cause an application to process an untrusted APNG may deny service by exhausting memory, even if the application only opens the image.",
  "mitigation": "Upgrade Pillow to version 13.0.0 or later. Until upgraded, do not process untrusted APNG files in services with limited memory.",
  "vendor": "python-pillow",
  "product": "Pillow",
  "affected": [
    {
      "affected_notes": [
        "8.1.0 - 12.3.0"
      ],
      "affected_ranges": [],
      "ecosystem": "pip",
      "fixed_versions": [
        "13.0.0"
      ],
      "package_name": "Pillow",
      "purl": "pkg:pypi/Pillow"
    }
  ],
  "cwes": [
    789
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0029,
  "epss_percentile": 0.2042,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.0106869,
  "t0_at": "2026-10-19T21:10:11.266000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T21:10:11.266000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T21:10:11.266000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112399"
    }
  }
}

published 2026-10-20 01:03Z
last change 2026-10-21 11:18Z

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.