CVE-2026-43907: OpenImageIO: Integer overflow in QueryRGBBufferSizeInternal leads to heap out-of-bounds write in DPX decoder (kCbYCr and kABGR)

Published May 14, 2026
·
Updated

Last updated 18 June 2026

Other sources

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 INTMIN 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 mdecodebuf.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.

MITRE

Affected Software

5 affected components
Openimageio Openimageio<3.0.18.0, <3.1.13.0
Openimageio Openimageio<3.0.18.0
Openimageio Openimageio>=3.1.4.0<3.1.13.0
Openimageio Openimageio=3.2.0.2-dev
debian/openimageio<=2.2.10.1+dfsg-1+deb11u1, <=2.4.7.1+dfsg-2, <=2.5.18.0+dfsg-1, <=2.5.19.1+dfsg-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/openimageio to a version that resolves this vulnerability.

    Fixed in 3.0.18.0
  2. Upgrade

    Upgrade debian/openimageio to a version that resolves this vulnerability.

    Fixed in 3.1.13.0
  3. Compensating control

    Until you can upgrade, avoid processing untrusted or adversary-supplied DPX files with OpenImageIO; isolate or sandbox any services that automatically ingest DPX images to limit exposure.

Event History

May 14, 2026
CVE Published
via MITRE·07:07 PM
Data Sourced
via MITRE·07:07 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeaknessAffected Software
Jun 17, 2026
Data Sourced
via Debian·11:42 PM
DescriptionAffected Software
Data Sourced
via Launchpad·11:42 PM
Description
Jun 18, 2026
Data Sourced
via Ubuntu·11:42 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-43907?

CVE-2026-43907 is classified as a high-severity vulnerability due to its potential for causing heap out-of-bounds write.

2

How do I fix CVE-2026-43907?

To mitigate CVE-2026-43907, update OpenImageIO to versions 3.0.18.0 or 3.1.13.0 or later.

3

What are the impacts of CVE-2026-43907 on systems using OpenImageIO?

CVE-2026-43907 can lead to arbitrary code execution and stability issues on systems utilizing affected versions of OpenImageIO.

4

Which versions of OpenImageIO are affected by CVE-2026-43907?

CVE-2026-43907 affects OpenImageIO versions prior to 3.0.18.0 and 3.1.13.0.

5

What types of formats are impacted by CVE-2026-43907 in OpenImageIO?

CVE-2026-43907 primarily affects the DPX decoder handling kCbYCr and kABGR formats in OpenImageIO.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203