Skip to main content
VulnerabilityPublished Updated

CVE-2025-61622: Apache Fory · Deserialization of Untrusted Data

Affects Apache ForySource CVE Database V5

0

Not known to be exploited · 45% EPSS · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
45.1% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Software Foundation Apache ForyAffected
  • =0.12.0
Fixed in–

AI-suggested

  1. Immediately upgrade Apache Fory to version 0.12.3 or later, which removes the insecure pickle fallback serializer.
  2. For legacy Pyfury users, migrate to updated versions or alternative serialization libraries that do not rely on unsafe deserialization mechanisms.
  3. Audit all applications and services to identify any usage of pyfory or pyfury libraries, especially where serialized data is received from untrusted or external sources.
  4. Implement strict input validation and enforce allowlisting of serialization formats to prevent fallback to unsafe serializers.
  5. Employ network segmentation and application-layer firewalls to limit exposure of services that deserialize external data.
  6. Monitor logs and network traffic for unusual deserialization attempts or anomalies indicative of exploitation attempts.
  7. Educate developers about the risks of deserializing untrusted data and promote secure coding practices.
  8. Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect and block exploitation attempts in real time.

Description

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.

References

Community reviews

Loading reviews…