CVE-2026-112390

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

GHSA-22hg-r758-rrw9 ↗EUVD-2026-104598 ↗

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 7.2.0 - 12.3.0
fixed in 13.0.0
CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
ETK-2026-2088Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/Pillow
1d 19h 28msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h02m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Pillow versions 7.2.0 through before 13.0.0 can loop indefinitely while processing certain MIC images. An attacker who can supply a specially formed MIC file may cause sustained CPU use when an application has olefile installed and reads image frame counts or saves all frames.

mitigation

Upgrade Pillow to version 13.0.0 or later. Until upgraded, restrict untrusted MIC uploads and avoid frame-count or all-frame processing for those files.

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 20:35Z
Δ 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 20:35Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2088",
  "cve_id": "CVE-2026-112390",
  "display_id": "CVE-2026-112390",
  "ghsa_id": "GHSA-22hg-r758-rrw9",
  "euvd_id": "EUVD-2026-104598",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Infinite-loop denial of service in Pillow MIC image handling",
  "summary": "Pillow versions 7.2.0 through before 13.0.0 can loop indefinitely while processing certain MIC images. An attacker who can supply a specially formed MIC file may cause sustained CPU use when an application has olefile installed and reads image frame counts or saves all frames.",
  "mitigation": "Upgrade Pillow to version 13.0.0 or later. Until upgraded, restrict untrusted MIC uploads and avoid frame-count or all-frame processing for those files.",
  "vendor": "python-pillow",
  "product": "Pillow",
  "affected": [
    {
      "affected_notes": [
        "7.2.0 - 12.3.0"
      ],
      "affected_ranges": [],
      "ecosystem": "pip",
      "fixed_versions": [
        "13.0.0"
      ],
      "package_name": "Pillow",
      "purl": "pkg:pypi/Pillow"
    }
  ],
  "cwes": [
    835
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/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": 10.80926995,
  "t0_at": "2026-10-19T20:35:39.189000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T20:35:39.189000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T20:35:39.189000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112390"
    }
  }
}

published 2026-10-19 21:26Z
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.