Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-68513: OpenEXR: Heap buffer overflow in PyOpenEXR from literal/prefixed RGB channel name collision

HighCVSS 7.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: openexr (Alpine:v3.24) 3.4.15-r0; openexr (Debian:14) 3.4.14-0.1; openexr (openSUSE:Tumbleweed) 3.4.14-1.1.

Low priority for now. Upgrade to openexr (Alpine:v3.24) 3.4.15-r0; openexr (Debian:14) 3.4.14-0.1; openexr (openSUSE:Tumbleweed) 3.4.14-1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. Versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13 contain a heap buffer overflow in PyOpenEXR triggered by a channel-name key collision between literal and prefixed RGB channels. When separate_channels=false, PyOpenEXR maps each physical channel name through channelNameToRGBA() and coalesces the results into a shared RGB array. A crafted flat scanline EXR that contains both a literal channel such as left and prefixed channels such as left.R, left.G, and left.B causes these names to collide, so the wrapper reuses an undersized two-dimensional NumPy array for the coalesced RGB slices and writes out of bounds when OpenEXR.File(path) decodes the pixels. This issue is fixed in versions 3.3.13 and 3.4.14.

Published
Aug 25, 2026
Updated
Sep 9, 2026
EPSS
0.1% · 9th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-68513

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for academysoftwarefoundation records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • AcademySoftwareFoundation openexr

    • >= 3.3.0, < 3.3.13, >= 3.4.0, < 3.4.14affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.24openexrbefore 3.4.15-r03.4.15-r0
Debian:14openexrbefore 3.4.14-0.13.4.14-0.1
openSUSE:Tumbleweedopenexrbefore 3.4.14-1.13.4.14-1.1
openSUSE:Tumbleweedpython-OpenEXRbefore 3.4.16-1.13.4.16-1.1

Same product

academysoftwarefoundation: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-68515OpenEXR: Heap out-of-bounds write in exrmultiview with subsampled channel union
    28Monitor
  • CVE-2026-59981OpenEXR: Heap OOB read in SampleCountChannel row when using nonzero dataWindow
    28Monitor
  • CVE-2026-59982OpenEXR: DWAA InputFile AC buffer overflow on ILP32 platforms
    28Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-62986Aug 25, 2026 · OpenEXR: PyOpenEXR deep prefixed RGB stale lane disclosure
    17Monitor
  • ← EarlierCVE-2026-65979Aug 25, 2026 · OpenEXR: Out-of-bounds read in HTJ2K decoder from unvalidated chunk header length (PLEN)
    26Monitor
  • Later →CVE-2026-68514Aug 25, 2026 · OpenEXR: Heap buffer overflow in PyOpenEXR from literal/prefixed RGB channel name collision in deep images
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:openexr3.4.15-r0 · Alpine:v3.24Package registry (OSV)
debian:openexr3.4.14-0.1 · Debian:14Package registry (OSV)
opensuse:openexr3.4.14-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python-OpenEXR3.4.16-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-591860 days apartOpenEXR: Heap out-of-bounds write in TiledRgbaInputFile via integer overflow on 32-bit (ILP32) builds
    28Monitor
  • CVE-2026-591870 days apartOpenEXR: exrmetrics deep pixelmode heap buffer overflow
    28Monitor
  • CVE-2026-685150 days apartOpenEXR: Heap out-of-bounds write in exrmultiview with subsampled channel union
    28Monitor
  • CVE-2026-685140 days apartOpenEXR: Heap buffer overflow in PyOpenEXR from literal/prefixed RGB channel name collision in deep images
    22Monitor

Not on record for this CVE: researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-122 · Heap-based Buffer Overflow

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records