CVE-2025-61622 in the critical feed json
Apache Fory, Apache Fory: Python RCE via unguarded pickle fallback serializer in pyfory
published last yr. modified last mo. also EUVD-2025-32708 , GHSA-538v-3wq9-4h3r , PYSEC-2026-490 , PYSEC-2026-491
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 47.8%
- EPSS 47.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
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.
Patch / fix
- pypi pyfory 0.12.3
- apache fory 0.12.3
- apache pyfory 0.12.3
- github.com/apache/fory@379b948 commit
- github.com/apache/fory#2629 pull request
- github.com/apache/fory/releases/tag/v0.12.3 release
Is CVE-2025-61622 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
47.78% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pyfory | >=0.12.0, <0.12.3 |
0.12.3 |
| pypi | pyfury | >=0.1.0, <=0.10.3 |
no fix listed |
Affected products
- Apache Software Foundation Apache Fory
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/apache/fory/pull/2629
web
-
github.com
/apache/fory/commit/379b948ecae5c3b849e5bdb3997978c9a163e40b
web
-
lists.apache.org
/thread/vfn9hp9qt06db5yo1gmj3l114o3o2csd
vendor-advisory, web, issue-tracking
-
openwall.com
/lists/oss-security/2025/09/29/3
web, mailing-list, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-61622
advisory
-
github.com
/apache/fory
package
-
github.com
/apache/fory/releases/tag/v0.12.3
web
-
pypi.org
/project/pyfory
package
-
github.com
/advisories/GHSA-538v-3wq9-4h3r
advisory
-
pypi.org
/project/pyfury
package
Sources
- CVE List CVE-2025-61622
- GitHub Advisory GHSA-538v-3wq9-4h3r
- NVD CVE-2025-61622
- OSV PYSEC-2026-490
- OSV PYSEC-2026-491
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.