CVE-2026-128066

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

GHSA-wqgw-9xfh-qf2g ↗

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 <= 12.3.0
fixed in 13.0.0
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-4329Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/Pillow
4h 26msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h45m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Pillow through 12.3.0 can consume excessive memory when processing crafted TIFF files or images containing EXIF metadata. An attacker who can cause an application to open or inspect attacker-controlled images may exhaust the process memory, including when EXIF metadata is accessed.

mitigation

Upgrade Pillow to version 13.0.0 or later. Until upgraded, avoid processing untrusted TIFF or EXIF-bearing images and avoid requesting EXIF metadata from untrusted 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.
–
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.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 22:47Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-12 22:47Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4329",
  "cve_id": "CVE-2026-128066",
  "display_id": "CVE-2026-128066",
  "ghsa_id": "GHSA-wqgw-9xfh-qf2g",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "anchored",
  "title": "Memory exhaustion in Pillow TIFF and EXIF parsing",
  "summary": "Pillow through 12.3.0 can consume excessive memory when processing crafted TIFF files or images containing EXIF metadata. An attacker who can cause an application to open or inspect attacker-controlled images may exhaust the process memory, including when EXIF metadata is accessed.",
  "mitigation": "Upgrade Pillow to version 13.0.0 or later. Until upgraded, avoid processing untrusted TIFF or EXIF-bearing images and avoid requesting EXIF metadata from untrusted files.",
  "vendor": "python-pillow",
  "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": [
    770
  ],
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.77801155,
  "t0_at": "2026-11-12T22:47:44.807000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T22:47:44.807000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T22:47:44.807000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-128066"
    }
  }
}

published 2026-11-12 23:17Z
last change 2026-11-12 23:56Z

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.