dbcve.org
ForyApplication · Apache

CVE-2025-61622

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-01
Fix available
A fix is available. Upgrade to after 0.12.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Deserialization vulnerability in pyfory/pyfury allows arbitrary code execution via pickle-fallback serializer. Attackers can craft malicious serialized data streams that trigger pickle.loads() during deserialization, leading to RCE when the application processes untrusted input.

MitigationUpgrade pyfory to version 0.12.3 or later which removes the vulnerable pickle fallback serializer, and audit code that deserializes data from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ForyApplication
Affected:>= 0.1.0, <= 0.10.3>= 0.12.0, <= 0.12.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed pyfory/pyfury version
    Run `pip show pyfory` or check the package metadata to retrieve the installed version number
    Affected if Version is 0.1.0 through 0.10.3, or 0.12.0 through 0.12.2
  2. Determine if pickle fallback is used
    Search codebase for Fury deserialization calls such as fury.deserialize() or Fury().deserialize() without explicit protocol or resolver configuration
    Affected if Default deserialization is used and attacker controls the serialized data stream
  3. Audit data source for deserialized content
    Identify code paths where serialized data from untrusted sources (network, file upload, user input, message queues) is passed to pyfory deserialization
    Affected if Application processes serialized data from untrusted or external sources through vulnerable pyfory versions

Environment is affected if pyfory version falls within 0.1.0-0.10.3 or 0.12.0-0.12.2 AND the application deserializes data from untrusted sources using the default pickle fallback serializer

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.12.2
Interim mitigation

Upgrade pyfory to version 0.12.3 or later which removes the vulnerable pickle fallback serializer, and audit code that deserializes data from untrusted sources.

Recommended fix High confidence

pyfory version 0.12.3 or later

  1. Check current installed version of pyfory or pyfury by running: pip show pyfory or pip show pyfury
  2. Upgrade pyfory to version 0.12.3 or later by running: pip install --upgrade pyfory>=0.12.3
  3. If using the legacy pyfury package, upgrade by running: pip install --upgrade pyfury>=0.12.3
  4. Verify the upgrade was successful by running: pip show pyfory and confirm the version is 0.12.3 or later
  5. Test application functionality to ensure deserialization still works correctly with the updated library
Caveat Users who relied on pickle fallback serialization for backward compatibility may need to update their serialization approach as pickle fallback has been removed in the fix

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fory Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61622 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data