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