← Back
CVE-2025-48071
Vulnerability in openexr (CVE-2025-48071)
Summary
vulnerability in openexr (CVE-2025-48071). Successful exploitation can lead to full system takeover. Exploitable via ``STORAGE_DEEP_SCANLINE``. Mitigation: upgrade to `3.3.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-48071** has been found in openexr.
Attackers can target a specific entry point like ``STORAGE_DEEP_SCANLINE`` 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.3.3** or later.
If unsure, ask your IT team or search "openexr CVE-2025-48071" on the vendor's site.
CVE-2025-48071 (openexr) — CWE-122 /
Attack vector: local / unauthenticated
Attack surface: `STORAGE_DEEP_SCANLINE` / `undo_zip_impl` / `uncompressed_size` / `unpacked_size`
Patched: `3.3.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-122) exists in openexr. Attackers reach the vulnerable code path via ``STORAGE_DEEP_SCANLINE`` without authentication.
📍 Affected scope
openexr — . Attack surface: `STORAGE_DEEP_SCANLINE` / `undo_zip_impl` / `uncompressed_size` / `unpacked_size`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.3.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.3.3ステージング環境で 3.3.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.3.0"},{"fixed":"3.3.3"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-48071
- advisory https://github.com/advisories/GHSA-h45x-qhg2-q375
- package https://github.com/AcademySoftwareFoundation/openexr
- package https://pypi.org/project/openexr
- web https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-h45x-qhg2-q375
- web https://github.com/AcademySoftwareFoundation/openexr/commit/916cc729e24aa16b86d82813f6e136340ab2876f
- web https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.3.3
- web https://github.com/ShielderSec/poc/tree/main/CVE-2025-48071