{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43905 exists.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-43905 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43905 exists.\n\nAffected product: Openimageio Openimageio. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-43905/ (Markdown: https://insights.sbomify.com/CVE-2026-43905/index.md)","id":"CVE-2026-43905","markdown":"https://insights.sbomify.com/CVE-2026-43905/index.md","name":"CVE-2026-43905","record":{"aliases":["DEBIAN-CVE-2026-43905","GHSA-pj45-cf3g-28gq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"OpenImageIO library","requires_auth":"none","summary":"A signed integer overflow in OpenImageIO's JPEG2000 handling can lead to heap overflow and potential code execution when processing crafted images.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openimageio","vendor":"openimageio"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"OpenImageIO: JPEG2000 (OpenJPH) signed integer overflow in buffer allocation","id":"CVE-2026-43905","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"openimageio:openimageio","products":["openimageio:openimageio"],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OpenImageIO: HEIF Heap overflow","id":"CVE-2026-43906"},"packages":[],"prev":{"headline":"OpenImageIO: Softimage PIC RLE decoder heap buffer overflow — longCount not clamped to image width","id":"CVE-2026-43904"},"products":["OpenImageIO"],"published":"2026-05-14","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-55192","kev_date_added":null,"published":"2025-01-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-55194","kev_date_added":null,"published":"2025-01-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-42299","kev_date_added":null,"published":"2023-11-02"},{"cvss_score":9.8,"headline":"Memory corruption in OpenImageIO","id":"CVE-2022-38143","kev_date_added":null,"published":"2022-12-23"},{"cvss_score":8.8,"headline":"OpenImageIO: Signed integer overflow in ConvertCbYCrYToRGB leads to heap out-of-bounds write in DPX 4:2:2 decoder","id":"CVE-2026-43908","kev_date_added":null,"published":"2026-05-14"},{"cvss_score":8.8,"headline":"OpenImageIO: Signed integer overflow in SwapRGBABytes loop index leads to out-of-bounds read/write in DPX ABGR decoder","id":"CVE-2026-43909","kev_date_added":null,"published":"2026-05-14"},{"cvss_score":8.8,"headline":"Integer overflow in n/a","id":"CVE-2023-42295","kev_date_added":null,"published":"2023-10-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["AcademySoftwareFoundation"]},"summary":"A signed integer overflow in OpenImageIO's JPEG2000 handling can lead to heap overflow and potential code execution when processing crafted images.","url":"https://insights.sbomify.com/CVE-2026-43905/"}