Skip to main content
CVE-2025-62515VulnerabilityPublished

CVE-2025-62515: marsupialtail quokka · Deserialization of Untrusted Data

Affects marsupialtail quokkaSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 59% 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 17 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
PyPIquokkapkg:pypi/quokkaOther threatsAffected
  • <=3.0.1
Fixed in–

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

AI-suggested

To mitigate CVE-2025-62515, European organizations should implement the following specific actions: 1) Immediately audit all quokka deployments to identify versions at or below 3.0.1 and FlightServer configurations exposing 0.0.0.0 interfaces. 2) Restrict network exposure by limiting FlightServer bindings to trusted internal IP addresses or localhost where possible, and enforce network segmentation and firewall rules to block untrusted access. 3) Disable or remove the use of pickle.loads() on untrusted data in custom code or configurations until patches are available. 4) Monitor network traffic for unusual or malformed pickled payloads targeting the set_configs action or other FlightServer endpoints. 5) Implement application-layer input validation or adopt safer serialization formats (e.g., JSON) that do not allow code execution. 6) Apply vendor patches or updates promptly once released; if no patches exist, consider upgrading to a fixed version or alternative frameworks. 7) Employ endpoint detection and response (EDR) tools to detect suspicious process executions or anomalous behavior on servers running quokka. 8) Conduct security awareness training for developers and administrators about the risks of unsafe deserialization. These measures go beyond generic advice by focusing on network configuration, code auditing, and monitoring tailored to quokka's architecture.

Description

pyquokka is a framework for making data lakes work for time series. In versions 0.3.1 and prior, the FlightServer class directly uses pickle.loads() to deserialize action bodies received from Flight clients without any sanitization or validation in the do_action() method. The vulnerable code is located in pyquokka/flight.py at line 283 where arbitrary data from Flight clients is directly passed to pickle.loads(). When FlightServer is configured to listen on 0.0.0.0, this allows attackers across the entire network to perform arbitrary remote code execution by sending malicious pickled payloads through the set_configs action. Additional vulnerability points exist in the cache_garbage_collect, do_put, and do_get functions where pickle.loads is used to deserialize untrusted remote data.

References

Community reviews

Loading reviews…