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

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

GHSA-6358-7h9p-8g5c ↗

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.
other:OpenEXR 3.5.0-3.5.2
fixed in 3.5.3
CWE-122 Heap-based Buffer Overflow
ETK-2026-3182Zero's internal tracking ID, independent of the CVE number., no cve assigned
cvss7.0ethiack provisional
6h 21msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
waiting for further signals−0h49mtrigger signal +0h
+2h
+4h
+6h

description

OpenEXRCore can write beyond an allocated buffer while decoding crafted ZSTD-compressed deep tiled EXR files. An attacker who can supply such a file to an application using the OpenEXRCore C API's single-pass decoding path may cause a crash or memory corruption.

mitigation

Upgrade OpenEXR to version 3.5.3 or later. Until upgrades are complete, avoid decoding untrusted deep tiled EXR files through the affected OpenEXRCore C API path.

fixed in 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
22m
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:38Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3182",
  "cve_id": null,
  "display_id": "ETK-2026-3182",
  "ghsa_id": "GHSA-6358-7h9p-8g5c",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Heap buffer overflow in OpenEXRCore deep tiled ZSTD decoding",
  "summary": "OpenEXRCore can write beyond an allocated buffer while decoding crafted ZSTD-compressed deep tiled EXR files. An attacker who can supply such a file to an application using the OpenEXRCore C API's single-pass decoding path may cause a crash or memory corruption.",
  "mitigation": "Upgrade OpenEXR to version 3.5.3 or later. Until upgrades are complete, avoid decoding untrusted deep tiled EXR files through the affected OpenEXRCore C API path.",
  "vendor": "other",
  "product": "other:OpenEXR",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "3.5.0-3.5.2"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "3.5.3"
      ],
      "package_name": "OpenEXR",
      "purl": null
    }
  ],
  "cwes": [
    122
  ],
  "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": 21.585422816666668,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-31T14:38:10+00:00",
      "days": -0.23019118741898148,
      "is_lower_bound": true,
      "measured_at": "2026-10-31T20:09:38.588707+00:00",
      "url": "https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-6358-7h9p-8g5c"
    }
  }
}

published 2026-10-31 15:34Z
last change 2026-10-31 19:43Z

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.