CVE-2026-43907

HIGHNVD 8.38.3
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
53(Track*)
EG Risk 53/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 15, 2026

Advisory Details (1)

Auto-updated May 14, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Integer overflow in QueryRGBBufferSizeInternal leads to heap out-of-bounds write in DPX decoder (kCbYCr and kABGR) · Advisory · AcademySoftwareFoundation/OpenImageIO · GitHub

https://github.com/AcademySoftwareFoundation/OpenImageIO/security/advisories/GHSA-cq46-hp4h-cvfr

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython-openimageio (1.6.11~dfsg0-1ubuntu1+esm2) @ xenial2026-08-23ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openimageio2.2.10.1+dfsg-1 ... 2.5.7.0+dfsg-1 (43 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openimageio2.4.12.0+dfsg-1 ... 2.5.7.0+dfsg-1 (18 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openimageio2.5.18.0+dfsg-1, 2.5.19.1+dfsg-1, 2.5.19.1+dfsg-2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openimageio2.5.18.0+dfsg-1, 2.5.19.1+dfsg-1, 2.5.19.1+dfsg-2

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 182 total refreshes for this CVE.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:31 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-11 07:53 UTCOSV refresh
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-23 17:37 UTCEG score recompute
  25. 2026-08-23 17:37 UTCVendor advisory
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-22 01:46 UTCEG score recompute
  3. 2026-08-22 01:46 UTCVendor advisory
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 19:32 UTCEG score recompute
  7. 2026-08-20 19:32 UTCVendor advisory
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 10:22 UTCEG score recompute
  12. 2026-08-17 10:22 UTCVendor advisory
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 03:55 UTCEG score recompute
  15. 2026-08-16 03:55 UTCVendor advisory
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-15 00:42 UTCVendor advisory
  19. 2026-08-14 13:33 UTCVendor advisory
  20. 2026-08-14 02:23 UTCEG score recompute
  21. 2026-08-14 02:23 UTCVendor advisory
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 02:07 UTCVendor advisory
  24. 2026-08-12 14:58 UTCEG score recompute
  25. 2026-08-12 14:58 UTCVendor advisory
  26. 2026-08-12 13:51 UTCEPSS rescore
  27. 2026-08-11 15:24 UTCEG score recompute
  28. 2026-08-11 15:24 UTCVendor advisory
  29. 2026-08-11 13:43 UTCEPSS rescore
  30. 2026-08-11 00:51 UTCEG score recompute
  31. 2026-08-11 00:51 UTCVendor advisory
  32. 2026-08-11 00:00 UTCEPSS rescore
  33. 2026-08-10 11:28 UTCVendor advisory
  34. 2026-08-10 00:08 UTCEG score recompute
  35. 2026-08-10 00:08 UTCVendor advisory
  36. 2026-08-09 13:46 UTCEPSS rescore
  37. 2026-08-09 12:59 UTCVendor advisory
  38. 2026-08-09 01:49 UTCEG score recompute
  39. 2026-08-09 01:49 UTCVendor advisory
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-08 05:23 UTCVendor advisory
  42. 2026-08-07 18:14 UTCEG score recompute
  43. 2026-08-07 18:14 UTCVendor advisory
  44. 2026-08-07 07:05 UTCVendor advisory
  45. 2026-08-06 19:54 UTCEG score recompute
  46. 2026-08-06 19:54 UTCVendor advisory
  47. 2026-08-06 13:46 UTCEPSS rescore
  48. 2026-08-06 08:45 UTCVendor advisory
  49. 2026-08-05 21:35 UTCEG score recompute
  50. 2026-08-05 21:35 UTCVendor advisory
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 10:38 UTCEPSS rescore
  54. 2026-08-03 18:59 UTCEG score recompute
  55. 2026-08-03 18:59 UTCVendor advisory
  56. 2026-08-03 10:36 UTCEPSS rescore
  57. 2026-08-02 18:54 UTCVendor advisory
  58. 2026-08-02 07:45 UTCEG score recompute
  59. 2026-08-02 07:45 UTCVendor advisory
  60. 2026-08-02 02:27 UTCEPSS rescore
  61. 2026-08-01 19:15 UTCEG score recompute
  62. 2026-08-01 19:15 UTCVendor advisory
  63. 2026-08-01 04:16 UTCEPSS rescore
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-28 15:36 UTCEPSS rescore
  67. 2026-07-27 14:13 UTCEPSS rescore
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-25 14:18 UTCEPSS rescore
  71. 2026-07-24 14:17 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 03:14 UTCEG score recompute
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-21 15:24 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43907?
CVE-2026-43907 is a high vulnerability published on May 14, 2026. 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…
When was CVE-2026-43907 disclosed?
CVE-2026-43907 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43907 actively exploited?
CVE-2026-43907 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.1% of all scored CVEs.
What is the CVSS score of CVE-2026-43907?
CVE-2026-43907 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-43907?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43907, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43907

Explore →

Is Your Infrastructure Affected by CVE-2026-43907?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.