CVE-2026-54920

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this weekElevated
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In versions 3.4.0 through 3.4.12, a reachable assertion failure in the HTJ2K decode path allows a crafted HTJ2K-compressed EXR file to cause an unconditional process abort in any application that calls exr_start_read() on untrusted input, resulting in denial of service. The crash is triggered by a QCD marker whose lower five bits are zero, which OpenEXR passes into the vendored OpenJPH library while constructing the codestream and evaluating its quantization delta parameters. OpenJPH uses an assertion rather than a recoverable error to validate those bits, so any invalid value calls abort() directly and cannot be intercepted by surrounding error handling, a problem compounded by OpenEXR wrapping only its internal HT header parser in error handling while leaving the later codestream read and construction calls unprotected. This issue has been resolved in version 3.4.13.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 25, 2026

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 16:22 UTCNVD update
  2. 2026-08-25 15:30 UTCEG score recompute
  3. 2026-08-25 15:29 UTCMITRE cvelistV5
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-25 01:17 UTCNVD update
  6. 2026-08-25 00:25 UTCEG score recompute
  7. 2026-08-25 00:25 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-54920?
CVE-2026-54920 is a publicly disclosed vulnerability published on August 25, 2026. OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In versions 3.4.0 through 3.4.12, a reachable assertion failure in the HTJ2K decode path allows a crafted HTJ2K-compressed EXR file to cause an unconditional process abort…
When was CVE-2026-54920 disclosed?
CVE-2026-54920 was first published in the National Vulnerability Database on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54920 actively exploited?
CVE-2026-54920 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.5% of all scored CVEs.
How do I remediate CVE-2026-54920?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54920, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54920

Explore →

Is Your Infrastructure Affected by CVE-2026-54920?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.