{"answers":{"affected":"3 open source packages ship an affected version, including pyquokka.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62515 exists.","fix":"No fix has been published for CVE-2025-62515 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-62515 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62515 exists.\n\nAffected packages and fixed versions:\n- pyquokka (PyPI): affected all versions up to 0.3.1; no fix listed\n- pyquokka (PyPI): affected all versions up to 0.3.1; no fix listed\n- pyquokka (PyPI): affected all versions up to 0.3.1; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62515/ (Markdown: https://insights.sbomify.com/CVE-2025-62515/index.md)","id":"CVE-2025-62515","markdown":"https://insights.sbomify.com/CVE-2025-62515/index.md","name":"CVE-2025-62515","record":{"aliases":["GHSA-f74j-gffq-vm9p","PYSEC-2026-503"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Python data lake framework","requires_auth":"none","summary":"Attackers can execute arbitrary code remotely by sending malicious pickled payloads to the FlightServer if it is configured to listen on all network interfaces.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Remote Code Execution by Pickle Deserialization via FlightServer in pyquokka","id":"CVE-2025-62515","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"Further research determined the issue is not a vulnerability.","id":"CVE-2025-62516"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.3.1"],"package":"pyquokka","purl":null,"source":"GHSA-f74j-gffq-vm9p"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.3.1"],"package":"pyquokka","purl":"pkg:pypi/pyquokka","source":"GHSA-f74j-gffq-vm9p"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.3.1"],"package":"pyquokka","purl":"pkg:pypi/pyquokka","source":"PYSEC-2026-503"}],"prev":{"headline":"`libparsec_crypto` does not check for weak order point of curve 25519","id":"CVE-2025-62514"},"products":["quokka"],"published":"2025-10-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-17","vendors":["marsupialtail"]},"summary":"Attackers can execute arbitrary code remotely by sending malicious pickled payloads to the FlightServer if it is configured to listen on all network interfaces.","url":"https://insights.sbomify.com/CVE-2025-62515/"}