High Memory corruption exploit reference

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

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.

Published May 14, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.5% (30-day exploitation probability)+6
Technical severity (high)+6
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.46%

ahead of 38% of scored CVEs · Oct 14, 2026

Affects

AcademySoftwareFoundation

OpenImageIO and 1 more

CVSS base

8.3

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (AcademySoftwareFoundation OpenImageIO, Openimageio Openimageio).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
AcademySoftwareFoundation	OpenImageIO	version < 3.0.18.0version >= 3.1.4.0-beta, < 3.1.13.0	Vulnerable	CVE Program (cve.org) e CISA ADP
Openimageio	Openimageio	< 3.0.18.0≥ 3.1.4.0 and < 3.1.13.0version 3.2.0.2-dev	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.3	CVSS 3.1	High	2.8	5.5	security-advisories@github.com via NIST National Vulnerability Database
8.3	CVSS 3.1	High	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-190 · Integer Overflow or Wraparound

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.46%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.

web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

2026
Affected products added · academysoftwarefoundation/openimageio
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 8.3
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
May 14, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

github.com/AcademySoftwareFoundation/OpenImageIO/security/advisories/GHSA-cq46-h
Exploit, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database

Elsewhere on this site

AcademySoftwareFoundation
every CVE for this vendor

Memory corruption
same class

CWE-190
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-43909 OpenImageIO: Signed integer overflow in SwapRGBABytes loop index leads to out-of-bounds read/write in DPX ABGR decoder May 14, 2026
Medium CVE-2026-43996 OpenImageIO: Integer wraparound in bounds check of decode_pixel leads to out-of-bounds read in TGA paletted image decoder May 14, 2026
High CVE-2026-43903 OpenImageIO: SGI RLE decoder heap buffer overflow OIIO_DASSERT bounds checks are no-ops in release builds May 14, 2026
High CVE-2026-43904 OpenImageIO: Softimage PIC RLE decoder heap buffer overflow — longCount not clamped to image width May 14, 2026
High CVE-2026-43905 OpenImageIO: JPEG2000 (OpenJPH) signed integer overflow in buffer allocation May 14, 2026
High CVE-2026-43906 OpenImageIO: HEIF Heap overflow May 14, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-43907 is "OpenImageIO: Integer overflow in QueryRGBBufferSizeInternal leads to heap out-of-bounds write in DPX decoder (kCbYCr and kABGR)", rated High. It affects OpenImageIO (AcademySoftwareFoundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.3 describes technical severity. EPSS 0.46% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.