# CVE-2026-43905: OpenImageIO: JPEG2000 (OpenJPH) signed integer overflow in buffer allocation

> A signed integer overflow in OpenImageIO's JPEG2000 handling can lead to heap overflow and potential code execution when processing crafted images.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** DEBIAN-CVE-2026-43905, GHSA-pj45-cf3g-28gq

## What is CVE-2026-43905?

CVE-2026-43905 is a high-severity vulnerability in Openimageio Openimageio, published on 14 May 2026. 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

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, jpeg2000input.cpp:395 computes buffer size as const int bufsize = w * h * ch * buffer_bpp using signed 32-bit arithmetic. When the product exceeds INT_MAX, the result wraps to 0 or a small value. m_buf.resize() allocates an undersized buffer, and subsequent pixel write loops cause heap overflow. Conditional on USE_OPENJPH build flag. This vulnerability is fixed in 3.0.18.0 and 3.1.13.0.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Openimageio Openimageio.

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

Upgrade to a fixed version.

## Is CVE-2026-43905 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43905 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-43905 and fix it if it is affected.

What it is: CVE-2026-43905 is a high-severity vulnerability in Openimageio Openimageio, published on 14 May 2026. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43905 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-43905/ (Markdown: https://insights.sbomify.com/CVE-2026-43905/index.md)
```

## Sources

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

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