ETK-2026-3189Zero's internal tracking ID, independent of the CVE number.

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

GHSA-638x-x7mr-89xc ↗

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 other:OpenEXR 3.3.0-3.3.14; 3.4.0-3.4.16; 3.5.0-3.5.2
fixed in 3.3.15, 3.4.17, 3.5.3
CWE-195 Signed to Unsigned Conversion Error
ETK-2026-3189Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:pypi/OpenEXR
cvss7.0ethiack provisional
5h 00msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+2h25m
0
+2h
+4h
+6h
+8h

description

OpenEXR's legacy Python InputFile.channel() API can perform an out-of-bounds memory write while decoding a crafted EXR file. An attacker must be able to supply an EXR file that the application processes through this legacy API; this can crash the process and permits file-influenced memory writes.

mitigation

Upgrade OpenEXR to 3.3.15, 3.4.17, 3.5.3 or later.

fixed in 3.3.15, 3.4.17, 3.5.3

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
14m
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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-31 14:37Z

this entry in the feed

GET /api/v1/feed/ETK-2026-3189

{
  "etk_id": "ETK-2026-3189",
  "cve_id": null,
  "display_id": "ETK-2026-3189",
  "ghsa_id": "GHSA-638x-x7mr-89xc",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Out-of-bounds write in OpenEXR legacy Python decoder",
  "summary": "OpenEXR's legacy Python `InputFile.channel()` API can perform an out-of-bounds memory write while decoding a crafted EXR file. An attacker must be able to supply an EXR file that the application processes through this legacy API; this can crash the process and permits file-influenced memory writes.",
  "mitigation": "Upgrade OpenEXR to 3.3.15, 3.4.17, 3.5.3 or later.",
  "vendor": "pip",
  "product": "other:OpenEXR",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "3.3.0-3.3.14",
        "3.4.0-3.4.16",
        "3.5.0-3.5.2"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "3.3.15",
        "3.4.17",
        "3.5.3"
      ],
      "package_name": "OpenEXR",
      "purl": "pkg:pypi/OpenEXR"
    }
  ],
  "cwes": [
    195
  ],
  "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": 14.204198666666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-31T14:37:27+00:00",
      "days": -0.3084858257523148,
      "is_lower_bound": true,
      "measured_at": "2026-10-31T22:01:40.208423+00:00",
      "url": "https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-638x-x7mr-89xc"
    }
  }
}

published 2026-10-31 17:04Z
last change 2026-10-31 21:57Z

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.