CVE-2025-62515
published 2025-10-17CVE-2025-62515: 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…
PriorityP268critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.76%
50.7th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| marsupialtail | quokka | <= 3.0.1 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
pyquokka is Vulnerable to Remote Code Execution by Pickle Deserialization via FlightServer
ghsa·2025-10-17
CVE-2025-62515 [CRITICAL] CWE-502 pyquokka is Vulnerable to Remote Code Execution by Pickle Deserialization via FlightServer
pyquokka is Vulnerable to Remote Code Execution by Pickle Deserialization via FlightServer
### Description
In the FlightServer class of the pyquokka framework, the do_action() method directly uses pickle.loads() to deserialize action bodies received from Flight clients without any sanitization or validation, which results in a remote code execution vulnerability. The vulnerable code is located in pyquokka/flight.py at line 283, where arbitrary data from Flight clients is directly passed to pickle.loads().
Even more concerning, when FlightServer is configured to listen on 0.0.0.0 (as shown in the provided server example at line 339), this allows attackers across the entire network to perform arbitrary remote code execution by sending malicious pickled payloads through the set_configs act
OSV
pyquokka is Vulnerable to Remote Code Execution by Pickle Deserialization via FlightServer
osv·2025-10-17
CVE-2025-62515 [CRITICAL] pyquokka is Vulnerable to Remote Code Execution by Pickle Deserialization via FlightServer
pyquokka is Vulnerable to Remote Code Execution by Pickle Deserialization via FlightServer
### Description
In the FlightServer class of the pyquokka framework, the do_action() method directly uses pickle.loads() to deserialize action bodies received from Flight clients without any sanitization or validation, which results in a remote code execution vulnerability. The vulnerable code is located in pyquokka/flight.py at line 283, where arbitrary data from Flight clients is directly passed to pickle.loads().
Even more concerning, when FlightServer is configured to listen on 0.0.0.0 (as shown in the provided server example at line 339), this allows attackers across the entire network to perform arbitrary remote code execution by sending malicious pickled payloads through the set_configs act
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-10-17
Published