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

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

GHSA-rjg8-982x-jhc2 ↗

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.
c/c++ other:OpenEXR 3.1.0-3.1.13; 3.2.0-3.2.11; 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
ETK-2026-3184Zero's internal tracking ID, independent of the CVE number., no cve assigned
cvss7.0ethiack provisional
5h 50msince last run
23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+1h33m
0
+2h
+4h
+6h
+8h

description

Affected OpenEXRCore releases can expose residual heap data in decoded pixels when they process a malformed DWA-compressed EXR file. An attacker needs to provide an EXR to a service that decodes it and makes the resulting pixel data available, such as an image preview or conversion service.

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
23m
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:39Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3184",
  "cve_id": null,
  "display_id": "ETK-2026-3184",
  "ghsa_id": "GHSA-rjg8-982x-jhc2",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Heap memory disclosure in OpenEXRCore DWA decoding",
  "summary": "Affected OpenEXRCore releases can expose residual heap data in decoded pixels when they process a malformed DWA-compressed EXR file. An attacker needs to provide an EXR to a service that decodes it and makes the resulting pixel data available, such as an image preview or conversion service.",
  "mitigation": "Upgrade openexr to 3.3.15, 3.4.17, 3.5.3 or later.",
  "vendor": "c/c++",
  "product": "other:OpenEXR",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "3.1.0-3.1.13",
        "3.2.0-3.2.11",
        "3.3.0-3.3.14",
        "3.4.0-3.4.16",
        "3.5.0-3.5.2"
      ],
      "ecosystem": "c/c++",
      "fixed_versions": [
        "3.3.15",
        "3.4.17",
        "3.5.3"
      ],
      "package_name": "openexr",
      "purl": null
    }
  ],
  "cwes": null,
  "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": 22.94209031666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-31T14:39:32+00:00",
      "days": -0.30709664731481484,
      "is_lower_bound": true,
      "measured_at": "2026-10-31T22:01:45.181861+00:00",
      "url": "https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-rjg8-982x-jhc2"
    }
  }
}

published 2026-10-31 16: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.