pyfory Known Vulnerabilities & Fixes
pyfory has 2 known security vulnerabilities in PyPI (Python). Upgrade to version 1.0.0 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 1.0.0
Upgrading to 1.0.0 or later resolves all 2 known vulnerabilities in pyfory. Run: pip install "pyfory>=1.0.0"
Is pyfory in your project?
Check if you're affected and upgrade to 1.0.0 to stay secure.
Security Summary
- 2 affected version ranges have been identified across these 2 advisories.
- 100% of known issues have a published fixed version.
- Remediation: pip install --upgrade pyfory
Vulnerabilities
2 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed Oct 1, 2025, most recently May 21, 2026 (232 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-48207 Apache Fory PyFory Deserialization of Untrusted Data | CRITICAL | 0.13.0, 0.13.1, 0.13.2, 0.14.0 (+4 more) | 1.0.0 |
| CVE-2025-61622 Apache Pyfory python is vulnerable to deserialization of untrusted data | CRITICAL | 0.12.0, 0.12.1, 0.12.2 | 0.12.3 |
About This Data
Vulnerability data for pyfory is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related PyPI (Python) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of pyfory.