# CVE-2025-12839: Academy Software Foundation OpenEXR EXR File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code by tricking users into opening malicious EXR files due to a heap-based buffer overflow in OpenEXR.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-12839, ECHO-ba7d-8327-9f35, GHSA-7q38-vqq7-45c9, JLSEC-2026-136, ROOT-OS-DEBIAN-11-CVE-2025-12839, ROOT-OS-DEBIAN-12-CVE-2025-12839, ROOT-OS-DEBIAN-13-CVE-2025-12839, UBUNTU-CVE-2025-12839

## What is CVE-2025-12839?

CVE-2025-12839 is a high-severity memory corruption vulnerability in Openexr Openexr, published on 23 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Academy Software Foundation OpenEXR EXR File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Academy Software Foundation OpenEXR. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the parsing of EXR files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-27947.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-12839?

It affects 1 product.


Products: Openexr Openexr.

## How do I fix CVE-2025-12839?

Apply the vendor's patch.

## Is CVE-2025-12839 being exploited?

There is no known exploitation of CVE-2025-12839 in the wild and no public exploit code.

## Other vulnerabilities in Openexr Openexr

- [CVE-2023-5841](https://insights.sbomify.com/CVE-2023-5841/): OpenEXR Heap Overflow in Scanline Deep Data Parsing (critical 9.1)
- [CVE-2026-41142](https://insights.sbomify.com/CVE-2026-41142/): OpenEXR is Vulnerable to Integer overflow in ImageChannel::resize leads to heap OOB write via OpenEXRUtil public API (high 8.8)
- [CVE-2026-42216](https://insights.sbomify.com/CVE-2026-42216/): OpenEXR: Out-of-bounds read in `IDManifest::init()` during prefix expansion (high 8.8)
- [CVE-2017-9111](https://insights.sbomify.com/CVE-2017-9111/): OpenEXR invalid write (high 8.8)
- [CVE-2017-9113](https://insights.sbomify.com/CVE-2017-9113/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12839 and fix it if it is affected.

What it is: CVE-2025-12839 is a high-severity memory corruption vulnerability in Openexr Openexr, published on 23 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-12839 in the wild and no public exploit code.

Affected product: Openexr Openexr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12839/ (Markdown: https://insights.sbomify.com/CVE-2025-12839/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12839
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12839
- OSV: https://osv.dev/vulnerability/CVE-2025-12839

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12839/
Summaries are generated and may contain mistakes; the official description above is the record.