# CVE-2026-43907: Integer overflow in OpenImageIO

> Integer overflow in OpenImageIO DPX decoder allows heap out-of-bounds write, potentially leading to code execution or crash when processing crafted images.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** DEBIAN-CVE-2026-43907, GHSA-cq46-hp4h-cvfr, UBUNTU-CVE-2026-43907

## What is CVE-2026-43907?

CVE-2026-43907 is a high-severity vulnerability in Openimageio Openimageio, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OpenImageIO is a toolset for reading, writing, and manipulating image files of any image file format relevant to VFX / animation. Prior to 3.0.18.0 and 3.1.13.0, a signed integer overflow in QueryRGBBufferSizeInternal() in DPXColorConverter.cpp leads to a heap-based out-of-bounds write when processing crafted DPX image files. The function computes buffer sizes using 32-bit signed integer arithmetic with negative multipliers (e.g., pixels * -3 * bytes for kCbYCr descriptors and pixels * -4 * bytes for kABGR descriptors), where a negative result is used as an in-band signal that no separate buffer is needed. When the pixel count is sufficiently large, the multiplication overflows INT_MIN and wraps to a small positive value. The caller in dpxinput.cpp interprets this positive value as a required buffer size, allocates an undersized heap buffer via m_decodebuf.resize(), and then writes the full image data into it via fread, resulting in a heap buffer overflow. An attacker can exploit this by crafting a DPX file that triggers the overflow, causing a denial of service (crash) or potentially arbitrary code execution through heap corruption in any application that reads pixel data using OpenImageIO. This vulnerability is fixed in 3.0.18.0 and 3.1.13.0.

Weakness: CWE-787 (Out-of-bounds Write), CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-43907?

It affects 1 product.


Products: Openimageio Openimageio.

## How do I fix CVE-2026-43907?

Upgrade to a fixed version.

## Is CVE-2026-43907 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43907 exists.

## Other vulnerabilities in Openimageio Openimageio

- [CVE-2024-55192](https://insights.sbomify.com/CVE-2024-55192/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-55194](https://insights.sbomify.com/CVE-2024-55194/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-42299](https://insights.sbomify.com/CVE-2023-42299/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-38143](https://insights.sbomify.com/CVE-2022-38143/): Memory corruption in OpenImageIO (critical 9.8)
- [CVE-2026-43908](https://insights.sbomify.com/CVE-2026-43908/): OpenImageIO: Signed integer overflow in ConvertCbYCrYToRGB leads to heap out-of-bounds write in DPX 4:2:2 decoder (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43907 and fix it if it is affected.

What it is: CVE-2026-43907 is a high-severity vulnerability in Openimageio Openimageio, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43907 exists.

Affected product: Openimageio Openimageio. 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-2026-43907/ (Markdown: https://insights.sbomify.com/CVE-2026-43907/index.md)
```

## Sources

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

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