CVE-2025-62515 Remote Code Execution by Pickle Deserialization via FlightServer in pyquokka
Attackers can execute arbitrary code remotely by sending malicious pickled payloads to the FlightServer if it is configured to listen on all network interfaces.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-62515?
CVE-2025-62515 is a critical unsafe deserialization vulnerability in marsupialtail quokka, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-502
Which versions are affected by CVE-2025-62515?
3 open source packages ship an affected version, including pyquokka.
| Package | Affected | Fixed in |
|---|---|---|
pyquokka PyPI | All versions to 0.3.1 | None |
pyquokka PyPI | All versions to 0.3.1 | None |
pyquokka PyPI | All versions to 0.3.1 | None |
How do I fix CVE-2025-62515?
No fix has been published for CVE-2025-62515 yet. Limit exposure of the affected software until one is available.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2025-62515 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62515 exists.
Sources
Also known as GHSA-f74j-gffq-vm9p, PYSEC-2026-503.