cve.bz

CVE-2025-61622 apache fory: Deserialization of Untrusted Data

9.8 criticalEPSS 49%Fix available

Critical (9.8) in apache fory. EPSS 49% estimated probability of exploitation activity in the next 30 days. Fixed in pyfory 0.12.3.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
49% (unchanged from 48% a week ago; 44% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-10-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-61622 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-61622?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-61622?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-61622 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-61622

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-61622](https://cve.bz/cve/badge/CVE-2025-61622.svg)](https://cve.bz/cve/CVE-2025-61622)

HTML:

<a href="https://cve.bz/cve/CVE-2025-61622"><img src="https://cve.bz/cve/badge/CVE-2025-61622.svg" alt="CVE-2025-61622"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Foryfrom 0.12.0 through 0.12.2
Apache Software Foundation Apache Foryfrom 0.1.0 through 0.10.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-538v-3wq9-4h3rPyPIpyfory>=0.12.0 <0.12.30.12.3
GHSA-538v-3wq9-4h3rPyPIpyfury>=0.1.0 <=0.10.3no fix published
PYSEC-2026-490PyPIpyfory>=0.12.0 <0.12.30.12.3
PYSEC-2026-491PyPIpyfury>=0.1.0 <=0.10.3no fix published

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON