CVE-2026-96778

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

GHSA-g7cr-3p24-7wf7 ↗

no check availablenot proven exploitable
awaiting cvepublic 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 9.4.0 - 12.3.0
fixed in 13.0.0
CWE-787 Out-of-bounds Write
ETK-2026-2174Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/Pillow
cvss7.0ethiack provisional
1d 00h 45msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −4.1dwaiting for further signals−1.0d
−4d
−3d
−2d
0

description

Pillow versions from 9.4.0 through versions before 13.0.0 can overflow a heap buffer while re-saving a JPEG that combines crafted metadata with an ICC color profile. An attacker who can supply such an image to an application that re-encodes it as JPEG while preserving the profile may crash the Python process and could potentially achieve code execution.

mitigation

Upgrade Pillow to version 13.0.0 or later. Until upgraded, avoid re-encoding untrusted images as JPEG while preserving embedded ICC profiles or comments.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2174",
  "cve_id": "CVE-2026-96778",
  "display_id": "CVE-2026-96778",
  "ghsa_id": "GHSA-g7cr-3p24-7wf7",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Heap buffer overflow in Pillow JPEG encoder",
  "summary": "Pillow versions from 9.4.0 through versions before 13.0.0 can overflow a heap buffer while re-saving a JPEG that combines crafted metadata with an ICC color profile. An attacker who can supply such an image to an application that re-encodes it as JPEG while preserving the profile may crash the Python process and could potentially achieve code execution.",
  "mitigation": "Upgrade Pillow to version 13.0.0 or later. Until upgraded, avoid re-encoding untrusted images as JPEG while preserving embedded ICC profiles or comments.",
  "vendor": "pip",
  "product": "Pillow",
  "affected": [
    {
      "affected_notes": [
        "9.4.0 - 12.3.0"
      ],
      "affected_ranges": [],
      "ecosystem": "pip",
      "fixed_versions": [
        "13.0.0"
      ],
      "package_name": "Pillow",
      "purl": "pkg:pypi/Pillow"
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.112552566666666,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-17T10:35:22+00:00",
      "days": -4.067625708043981,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T12:12:44.895791+00:00",
      "url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-g7cr-3p24-7wf7"
    }
  }
}

published 2026-10-20 12:22Z
last change 2026-10-21 11:52Z

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.