CVE-2025-61622: Apache Fory, Apache Fory: Python RCE via unguarded pickle fallback serializer in pyfory
Noroxi assessment
Priority: Plan (action score 53/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 45.1% (FIRST EPSS); higher than 98.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: pyfory (PyPI) 0.12.3.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Upgrade to pyfory (PyPI) 0.12.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 1, 2025
- Updated
- Oct 9, 2026
- EPSS
- 45.1% · 98th percentile
- CWE
- CWE-502
Report tools
Action score
53
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 14 / 30 · 45.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | fory | cpe:2.3:a:apache:fory |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache fory0.1.0 and later · up to 0.10.3 inclusive
- apache fory0.12.0 and later · up to 0.12.2 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache Fory
- 0.12.0 and later · up to and including 0.12.2affected · semver
- 0.1.0 and later · up to and including 0.10.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | pyfory | from 0.12.0 · before 0.12.3 | 0.12.3 |
| PyPI | pyfury | from 0.1.0 · up to and including 0.10.3 | — |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-71558Apache Fory: Heap type confusion in C++ polymorphic smart-pointer deserialization39Monitor
- CVE-2026-64606Apache Fory, Apache Fory: Class-registration bypass through an auto-admitted SerializedLambda capturing interface39Monitor
- CVE-2026-64608Apache Fory: Heap type confusion and out-of-bounds read/write in C++ compatible-mode field-skip paths39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-59328Sep 15, 2025 · Apache Fory: Denial of Service (DoS) due to Deserialization of Untrusted malicious large Data26Monitor
- Later →CVE-2026-48207May 21, 2026 · Apache Fory: PyFory ReduceSerializer Incomplete Policy Enforcement39Monitor
- Later →CVE-2026-50076Jun 4, 2026 · Apache Fory: Java ReplaceResolverSerializer deserialization checks bypass36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PyPI:pyfory | 0.12.3 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:4 | 2025-10-03 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+2 d
- TodayOct 28, 2026+392 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Mapta / BugBunny_aireporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-48207232 days apartApache Fory: PyFory ReduceSerializer Incomplete Policy Enforcement39Monitor
- CVE-2026-64606293 days apartApache Fory, Apache Fory: Class-registration bypass through an auto-admitted SerializedLambda capturing interface39Monitor
- CVE-2026-64608293 days apartApache Fory: Heap type confusion and out-of-bounds read/write in C++ compatible-mode field-skip paths39Monitor
- CVE-2026-71558310 days apartApache Fory: Heap type confusion in C++ polymorphic smart-pointer deserialization39Monitor
- CVE-2026-50076246 days apartApache Fory: Java ReplaceResolverSerializer deserialization checks bypass36Monitor
- CVE-2026-71560310 days apartApache Fory: Out-of-bounds heap read in C++ struct deserializer tagged-int fast-path36Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-25-0308 · Oct 2, 2025(Python Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-502 · Deserialization of Untrusted DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
Data received over the network is deserialized into the language’s native object format without verifying its source. Code paths inside the object can be triggered during deserialization.
The bug in code
The whole CWE-502 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
payload = sock.recv(65536)
job = pickle.loads(payload)Fixed
payload = sock.recv(65536)
if not hmac.compare_digest(sign(payload), header_sig):
raise PermissionError("invalid signature")
job = JobSchema.validate(json.loads(payload))Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.