Skip to main content
VulnerabilityPublished Updated

CVE-2025-62703: Fugue is Vulnerable to Remote Code Execution by Pickle Deserialization via FlaskRPCServer

Affects fugueSource GCVE Database

0
Compare
Authoritative record:CVE-2025-62703· High 8.8

Not known to be exploited · CVSS 8.8 High.

Data as of 19 Nov 2026, 02:54 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.8
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
PyPIfugueAffected
  • <=0.9.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should replace the unsafe pickle deserialization with safer serialization methods such as JSON, Protocol Buffers, or MessagePack. If pickle usage is unavoidable, implement a custom Unpickler restricting allowed classes. Network exposure should be minimized by binding the RPC server to localhost (127.0.0.1) instead of 0.0.0.0 for internal use only. Additionally, authentication and authorization mechanisms should be implemented to restrict access. Clear security warnings should be displayed when the service is started on public interfaces.

Description

Fugue framework versions up to 0.9.2 contain a remote code execution vulnerability due to unsafe deserialization of pickle data in its RPC server implementation. The _decode() function uses cloudpickle.loads() without sanitization, allowing attackers to send crafted serialized objects that execute arbitrary code on the server. This risk is especially critical when the RPC server is bound to a public network interface such as 0.0.0.0. The vulnerability can lead to full system compromise, data exfiltration, lateral movement, denial of service, and persistent backdoors. Mitigations include replacing unsafe deserialization methods, restricting network exposure, and adding authentication.

References

Community reviews

Loading reviews…