{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39886 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-39886 is a medium-severity vulnerability in Openexr Openexr, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-39886 and fix it if it is affected.\n\nWhat it is: CVE-2026-39886 is a medium-severity vulnerability in Openexr Openexr, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39886 exists.\n\nAffected product: Openexr Openexr. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-39886/ (Markdown: https://insights.sbomify.com/CVE-2026-39886/index.md)","id":"CVE-2026-39886","markdown":"https://insights.sbomify.com/CVE-2026-39886/index.md","name":"CVE-2026-39886","record":{"aliases":["BELL-CVE-2026-39886","DEBIAN-CVE-2026-39886","GHSA-r3mr-mx8q-jcw5","JLSEC-2026-806","UBUNTU-CVE-2026-39886"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenEXR image library","requires_auth":"none","summary":"A signed integer overflow in OpenEXR's HTJ2K decompression allows heap out-of-bounds writes via crafted files, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openexr","vendor":"openexr"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. Versions 3.4.0 through 3.4.9 have a signed integer overflow vulnerability in OpenEXR's HTJ2K (High-Throughput JPEG 2000) decompression path. The `ht_undo_impl()` function in `src/lib/OpenEXRCore/internal_ht.cpp` accumulates a bytes-per-line value (`bpl`) using a 32-bit signed integer with no overflow guard. A crafted EXR file with 16,385 FLOAT channels at the HTJ2K maximum width of 32,767 causes `bpl` to overflow `INT_MAX`, producing undefined behavior confirmed by UBSan. On an\nallocator-permissive host where the required ~64 GB allocation succeeds, the wrapped negative `bpl` value would subsequently be used as a per-scanline pointer advance, which would produce a heap out-of-bounds write. On a memory-constrained host, the allocation fails before `ht_undo_impl()` is entered. This is the second distinct integer overflow in `ht_undo_impl()`. CVE-2026-34545 addressed a different overflow in the same function — the `int16_t p` pixel-loop counter at line ~302 that overflows when iterating over channels whose `width` exceeds 32,767. The CVE-2026-34545 fix did not touch the `int bpl` accumulator at line 211, which is the subject of this advisory. The `bpl` accumulator was also not addressed by any of the 8 advisories in the 2026-04-05 v3.4.9 release batch. This finding is structurally identical to CVE-2026-34588 (PIZ `wcount*nx` overflow in `internal_piz.c`) and should be remediated with the same pattern. The CVE-2026-34588 fix did not touch `internal_ht.cpp`. Version 3.4.10 contains a remediation that addresses the vulnerability in `internal_ht.cpp`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"OpenEXR has HTJ2K Signed Integer Overflow in ht_undo_impl()","id":"CVE-2026-39886","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"openexr:openexr","products":["openexr:openexr"],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"PraisonAIAgents has a sandbox escape via exception frame traversal in `execute_code` (subprocess mode)","id":"CVE-2026-39888"},"packages":[],"prev":{"headline":"FrontMCP Affected by SSRF via $ref Dereferencing in Untrusted OpenAPI Specifications","id":"CVE-2026-39885"},"products":["openexr"],"published":"2026-04-21","related":[{"cvss_score":9.1,"headline":"OpenEXR Heap Overflow in Scanline Deep Data Parsing","id":"CVE-2023-5841","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":8.8,"headline":"OpenEXR is Vulnerable to Integer overflow in ImageChannel::resize leads to heap OOB write via OpenEXRUtil public API","id":"CVE-2026-41142","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":8.8,"headline":"OpenEXR: Out-of-bounds read in `IDManifest::init()` during prefix expansion","id":"CVE-2026-42216","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":8.8,"headline":"OpenEXR invalid write","id":"CVE-2017-9111","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9113","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9115","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":8.7,"headline":"OpenEXR: Heap information disclosure in PXR24 decompression via unchecked decompressed size (undo_pxr24_impl)","id":"CVE-2026-34543","kev_date_added":null,"published":"2026-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-21","vendors":["AcademySoftwareFoundation"]},"summary":"A signed integer overflow in OpenEXR's HTJ2K decompression allows heap out-of-bounds writes via crafted files, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-39886/"}