← Back
CVE-2025-64712
Path Traversal in unstructured (CVE-2025-64712)
Summary
path traversal in unstructured (CVE-2025-64712). Successful exploitation can lead to full system takeover. Exploitable via ``partition_msg``. Mitigation: upgrade to `0.18.18` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-64712** has been found in unstructured.
Attackers can target a specific entry point like ``partition_msg`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade unstructured to **0.18.18** or later.
If unsure, ask your IT team or search "unstructured CVE-2025-64712" on the vendor's site.
CVE-2025-64712 (unstructured) — CWE-22 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `partition_msg`
Patched: `0.18.18` — 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
**Path traversal** (CWE-22) exists in unstructured. Attackers reach the vulnerable code path via ``partition_msg`` without authentication.
📍 Affected scope
unstructured — . Attack surface: `partition_msg`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.18.18**.
🛡️ 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 'unstructured' .` 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 'unstructured' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `unstructured` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade unstructured to 0.18.18ステージング環境で 0.18.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
unstructured
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.18.18"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-64712
- package https://github.com/Unstructured-IO/unstructured
- web https://github.com/Unstructured-IO/unstructured/security/advisories/GHSA-gm8q-m8mv-jj5m
- web https://github.com/Unstructured-IO/unstructured/commit/b01d35b2373fd087d2e15162b9c021663c97155d