CVE-2026-45696 Vulnerability Analysis & Exploit Details

CVE-2026-45696
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2026-45696 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-45696 Details

Status: Analyzed

Last updated: 🕑 26 Jun 2026, 02:08 UTC
Originally published on: 🕘 18 Jun 2026, 21:16 UTC

Time between publication and last update: 7 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2026-45696 Vulnerability Summary

CVE-2026-45696: 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.11, the HTJ2K (High-Throughput JPEG 2000) decoder, ht_undo_impl() in OpenEXRCore is vulnerable to a heap-buffer-overflow READ. The ht_undo_imp function copies decoded pixels out of a per-line OpenJPH buffer using the EXR channel's declared width as the iteration count. The codestream embedded in the EXR chunk can declare different (smaller) tile/line dimensions than the EXR header advertises, but ht_undo_impl() does not validate this — it pulls width 32-bit samples from cur_line->i32[] without checking the OpenJPH line buffer's actual length. A crafted EXR file produces a 4-byte heap-buffer-overflow READ immediately after a buffer allocated by ojph::local::codestream::finalize_alloc(). The bug is reachable through the standard scanline-decode entry point used by every consumer of exr_decoding_run/Imf::checkOpenEXRFile, including thumbnailers, asset pipelines, and the exrcheck utility — i.e. any application that opens untrusted EXR files. The result is a deterministic crash (DoS) and potential adjacent-heap leak. This issue has been fixed in version 3.4.12.

Assessing the Risk of CVE-2026-45696

Access Complexity Graph

The exploitability of CVE-2026-45696 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-45696

CVE-2026-45696 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-45696, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-45696, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-45696 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-45696 poses no threat to data integrity.
  • Availability: High
    CVE-2026-45696 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-45696 References

External References

CWE Common Weakness Enumeration

CWE-122

CAPEC Common Attack Pattern Enumeration and Classification

  • Forced Integer Overflow CAPEC-92 This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.

Vulnerable Configurations

  • cpe:2.3:a:openexr:openexr:3.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.0:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.0:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.0:alpha:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.0:alpha:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.1:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.1:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.1:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.1:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.1:rc2:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.1:rc2:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.2:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.2:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.2:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.2:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.2:rc2:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.2:rc2:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.3:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.3:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.3:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.3:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.3:rc2:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.3:rc2:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.3:rc3:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.3:rc3:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.4:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.4:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.4:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.4:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.4:rc2:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.4:rc2:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.5:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.5:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.5:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.5:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.6:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.6:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.6:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.6:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.7:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.7:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.7:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.7:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.8:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.8:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.8:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.8:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.9:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.9:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.9:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.9:rc:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.10:-:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.10:-:*:*:*:*:*:*
  • cpe:2.3:a:openexr:openexr:3.4.10:rc:*:*:*:*:*:*
    cpe:2.3:a:openexr:openexr:3.4.10:rc:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-45696: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-15619 – A weakness has been identified in mosaxiv clawlet up to 0.2.10. The impacted element is the function web_fetch of the file tools/tool_web_fetch.go ...
  • CVE-2026-15618 – A security flaw has been discovered in mosaxiv clawlet up to 0.2.10. The affected element is the function guardExecCommand of the file tools/tool_e...
  • CVE-2026-58489 – HedgeDoc is an open source, real-time collaborative markdown notes application. Prior to 1.11.0, the GitHub Gist export flow created an OAuth2  sta...
  • CVE-2026-58486 – HedgeDoc is an open source, real-time, collaborative, markdown notes application. Prior to version 1.11.0, HedgeDoc was vulnerable to a YAML alias ...
  • CVE-2026-58102 – Crypt::OpenSSL::X509 versions before 2.1.3 for Perl allow a heap out-of-bounds read via a long certificate extension OID in hv_exts. When building...