CVE-2026-26981: PYSEC-2026-2849 - OpenEXR has heap-buffer-overflow via signed integer underflow in ImfContextInit.cpp

CVE-2026-26981 · Severity: low · CVSS 3.1 · Published 2026-07-13

OpenEXR has heap-buffer-overflow via signed integer underflow in ImfContextInit.cpp

Technologies: OpenEXR (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-26981 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-26981 being exploited in the wild.
How severe is CVE-2026-26981?
Low severity, with a CVSS score of 3.1, published 13 July 2026.
Which products and versions are affected?
OpenEXR (PyPI) ECOSYSTEM:introduced=3.3.0,fixed=3.3.7, ECOSYSTEM:introduced=3.3.0,fixed=3.3.7,introduced=3.4.0,fixed=3.4.5.
Is there a fix for CVE-2026-26981?
Yes. OpenEXR (PyPI): upgrade to 3.3.7, 3.4.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-26981?
Check whether you run OpenEXR (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • OpenEXR (PyPI): upgrade to 3.3.7, 3.4.5 or later
    pip install "OpenEXR>=3.4.5"

Affected products

  • OpenEXR (PyPI) ECOSYSTEM:introduced=3.3.0,fixed=3.3.7, ECOSYSTEM:introduced=3.3.0,fixed=3.3.7,introduced=3.4.0,fixed=3.4.5

Identifiers

  • CVE-2026-26981
  • GHSA-q6vj-wxvf-5m8c
  • PYSEC-2026-2849

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.