Disclosure summary
Deserialization of untrusted data in python in pyfory versions 0.12.0 through 0.12.2, or the legacy pyfury versions from 0.1.0 through 0.10.3: allows arbitrary code execution. An application is vulnerable if it reads pyfory serialized data from untrusted sources. An attacker can craft a data stream that selects pickle-fallback serializer during deserialization, leading to the execution of `pickle.loads`, which is vulnerable to remote code execution. Users are recommended to upgrade to pyfory version 0.12.3 or later, which has removed pickle fallback serializer and thus fixes this issue.
Source-reported weakness categories
CWE-502
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
NIST NVD · NVD-CVE-2025-61622
Open original source · Updated Oct 09, 2026
Only CPE matches marked vulnerable=true are indexed. AND/OR platform conditions must be checked in the original NVD record.
| Vendor | Product / association | Version / bounds |
|---|---|---|
| apache | fory | * · versionStartIncluding: 0.12.0 · versionEndIncluding: 0.12.2 |
Indexed product associations
These cached associations support search and triage. Confirm applicability, platform conditions, and fixed versions in the original record.
| Vendor | Product | Version | Source / relationship |
|---|---|---|---|
| apache | fory | * | nvd / vulnerable |
Original records & references
- NIST NVD record
- CVE Program record
- security@apache.org — Issue Tracking, Vendor Advisory
GitHub repository matches
Repository matches are links and GitHub-supplied metadata only. They are not verified working proof-of-concept code. Each supported query is bounded to ten pages and at most 1,000 indexed results. This is not a complete index of GitHub or public exploit research. Coverage can also be limited by provider availability, rate limits, rejected metadata, incomplete search results, manual review, and the recorded refresh time.
No stored repository matches
Repository discovery has not recorded an update for this CVE yet.
Discovery progress
0 of 3 discovery queries finished. GitHub returned 0 indexed results; 0 malformed or disallowed results were rejected.
No discovery update has been recorded for this CVE.
View all 0 stored repository matches
PUBLISHED 2025-10-01T10:15:34+00:00
MODIFIED 2026-10-09T09:10:00+00:00
INGESTED 2026-10-11T00:50:24+00:00