{"answers":{"affected":"7 open source packages ship an affected version, including openexr and OpenEXR. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64183 exists.","fix":"Upgrade openexr to a fixed version for your release line: 3.2.5, 3.3.6 or 3.4.3.","what":"CVE-2025-64183 is a medium-severity use after free vulnerability in Openexr Openexr, published on 10 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64183 and fix it if it is affected.\n\nWhat it is: CVE-2025-64183 is a medium-severity use after free vulnerability in Openexr Openexr, published on 10 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64183 exists.\n\nAffected packages and fixed versions:\n- openexr (PyPI): affected from 3.2.0; fixed in 3.2.5, 3.3.6, 3.4.3\n- openexr (PyPI): affected from 3.2.0; fixed in 3.2.5\n- openexr (PyPI): affected from 3.3.0; fixed in 3.3.6\n- openexr (PyPI): affected from 3.4.0; fixed in 3.4.3\n- OpenEXR (PyPI): affected from 3.2.0; fixed in 3.2.5\n- OpenEXR (PyPI): affected from 3.3.0; fixed in 3.3.6\n- OpenEXR (PyPI): affected from 3.4.0; fixed in 3.4.3\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-2025-64183/ (Markdown: https://insights.sbomify.com/CVE-2025-64183/index.md)","id":"CVE-2025-64183","markdown":"https://insights.sbomify.com/CVE-2025-64183/index.md","name":"CVE-2025-64183","record":{"aliases":["GHSA-57cw-j6vp-2p9m","JLSEC-2026-139","PYSEC-2026-2844"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OpenEXR image library","requires_auth":"none","summary":"A use-after-free vulnerability in OpenEXR's Python bindings allows attackers to execute arbitrary code or cause denial of service via crafted EXR files.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openexr","vendor":"openexr"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In versions 3.2.0 through 3.2.4, 3.3.0 through 3.3.5, and 3.4.0 through 3.4.2, there is a use-after-free in PyObject_StealAttrString of pyOpenEXR_old.cpp. The legacy adapter defines PyObject_StealAttrString that calls PyObject_GetAttrString to obtain a new reference, immediately decrefs it, and returns the pointer. Callers then pass this dangling pointer to APIs like PyLong_AsLong/PyFloat_AsDouble, resulting in a use-after-free. This is invoked in multiple places (e.g., reading PixelType.v, Box2i, V2f, etc.) Versions 3.2.5, 3.3.6, and 3.4.3 fix the issue.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"OpenEXR has use after free in PyObject_StealAttrString","id":"CVE-2025-64183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"openexr:openexr","products":["openexr:openexr"],"type":"use_after_free","year":"2025"},"n_packages":7,"n_references":2,"next":{"headline":"Dosage vulnerable to Directory Traversal through crafted HTTP responses","id":"CVE-2025-64184"},"packages":[{"ecosystem":"PyPI","fixed":["3.2.5"],"introduced":["3.2.0"],"last_affected":[],"package":"OpenEXR","purl":null,"source":"GHSA-57cw-j6vp-2p9m"},{"ecosystem":"PyPI","fixed":["3.3.6"],"introduced":["3.3.0"],"last_affected":[],"package":"OpenEXR","purl":null,"source":"GHSA-57cw-j6vp-2p9m"},{"ecosystem":"PyPI","fixed":["3.4.3"],"introduced":["3.4.0"],"last_affected":[],"package":"OpenEXR","purl":null,"source":"GHSA-57cw-j6vp-2p9m"},{"ecosystem":"PyPI","fixed":["3.2.5","3.3.6","3.4.3"],"introduced":["3.2.0","3.3.0","3.4.0"],"last_affected":[],"package":"openexr","purl":"pkg:pypi/openexr","source":"PYSEC-2026-2844"},{"ecosystem":"PyPI","fixed":["3.2.5"],"introduced":["3.2.0"],"last_affected":[],"package":"openexr","purl":"pkg:pypi/openexr","source":"GHSA-57cw-j6vp-2p9m"},{"ecosystem":"PyPI","fixed":["3.3.6"],"introduced":["3.3.0"],"last_affected":[],"package":"openexr","purl":"pkg:pypi/openexr","source":"GHSA-57cw-j6vp-2p9m"},{"ecosystem":"PyPI","fixed":["3.4.3"],"introduced":["3.4.0"],"last_affected":[],"package":"openexr","purl":"pkg:pypi/openexr","source":"GHSA-57cw-j6vp-2p9m"}],"prev":{"headline":"OpenEXR has buffer overflow in PyOpenEXR_old's channels() and channel()","id":"CVE-2025-64182"},"products":["openexr"],"published":"2025-11-10","related":[{"cvss_score":9.1,"headline":"OpenEXR Heap Overflow in Scanline Deep Data Parsing","id":"CVE-2023-5841","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":8.8,"headline":"OpenEXR is Vulnerable to Integer overflow in ImageChannel::resize leads to heap OOB write via OpenEXRUtil public API","id":"CVE-2026-41142","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":8.8,"headline":"OpenEXR: Out-of-bounds read in `IDManifest::init()` during prefix expansion","id":"CVE-2026-42216","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":8.8,"headline":"OpenEXR invalid write","id":"CVE-2017-9111","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9113","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9115","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":8.7,"headline":"OpenEXR: Heap information disclosure in PXR24 decompression via unchecked decompressed size (undo_pxr24_impl)","id":"CVE-2026-34543","kev_date_added":null,"published":"2026-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-11-14","vendors":["AcademySoftwareFoundation"]},"summary":"A use-after-free vulnerability in OpenEXR's Python bindings allows attackers to execute arbitrary code or cause denial of service via crafted EXR files.","url":"https://insights.sbomify.com/CVE-2025-64183/"}