← Back
CVE-2025-64182
Vulnerability in openexr (CVE-2025-64182)
Summary
vulnerability in openexr (CVE-2025-64182). Successful exploitation can lead to full system takeover. Exploitable via ``int``. Mitigation: upgrade to `3.4.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-64182** has been found in openexr.
Attackers can target a specific entry point like ``int`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade openexr to **3.4.3** or later.
If unsure, ask your IT team or search "openexr CVE-2025-64182" on the vendor's site.
CVE-2025-64182 (openexr) — CWE-120 /
Attack vector: local / unauthenticated
Attack surface: `int` / `typeSize` / `size_t` / `PyBytes_FromStringAndSize`
Patched: `3.4.3` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-120) exists in openexr. Attackers reach the vulnerable code path via ``int`` without authentication.
📍 Affected scope
openexr — . Attack surface: `int` / `typeSize` / `size_t` / `PyBytes_FromStringAndSize`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.4.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'openexr' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openexr' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `openexr` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade openexr to 3.4.3ステージング環境で 3.4.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
openexr
[{"type":"ECOSYSTEM","events":[{"introduced":"3.4.0"},{"fixed":"3.4.3"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-64182
- advisory https://github.com/advisories/GHSA-vh63-9mqx-wmjr
- package https://github.com/AcademySoftwareFoundation/openexr
- package https://pypi.org/project/openexr
- web https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-vh63-9mqx-wmjr
- web https://github.com/AcademySoftwareFoundation/openexr/blob/b3a19903db0672c63055023aa788e592b16ec3c5/src/wrappers/python/PyOpenEXR_old.cpp#L528-L536