{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11039 exists.","fix":"No fix has been published for CVE-2024-11039 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-11039 is a high-severity unsafe deserialization vulnerability in binary-husky/gpt_academic, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-11039 and fix it if it is affected.\n\nWhat it is: CVE-2024-11039 is a high-severity unsafe deserialization vulnerability in binary-husky/gpt_academic, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11039 exists.\n\nAffected product: binary-husky/gpt_academic. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2024-11039/ (Markdown: https://insights.sbomify.com/CVE-2024-11039/index.md)","id":"CVE-2024-11039","markdown":"https://insights.sbomify.com/CVE-2024-11039/index.md","name":"CVE-2024-11039","record":{"aliases":["GHSA-gf99-rrrr-wjqh"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GPT academic tool","requires_auth":"low_privilege","summary":"Attackers can achieve remote command execution via pickle deserialization in the Latex error correction plugin of gpt_academic.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"gpt_academic","vendor":"binary-husky"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"A pickle deserialization vulnerability exists in the Latex English error correction plug-in function of binary-husky/gpt_academic versions up to and including 3.83. This vulnerability allows attackers to achieve remote command execution by deserializing untrusted data. The issue arises from the inclusion of numpy in the deserialization whitelist, which can be exploited by constructing a malicious compressed package containing a merge_result.pkl file and a merge_proofread_en.tex file. The vulnerability is fixed in commit 91f5e6b.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Deserialization of Untrusted Data in binary-husky/gpt_academic","id":"CVE-2024-11039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Remote Code Execution in vllm-project/vllm","id":"CVE-2024-11041"},"packages":[],"prev":{"headline":"Code injection in WPB Popup for Contact Form 7 – Showing Contact Form 7 Popup on Button Click","id":"CVE-2024-11038"},"products":["binary-husky/gpt_academic"],"published":"2025-03-20","related":[{"cvss_score":9.8,"headline":"GPT Academic run_in_subprocess_wrapper_func Deserialization of Untrusted Data Remote Code Execution Vulnerability","id":"CVE-2026-0763","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":9.8,"headline":"GPT Academic upload Deserialization of Untrusted Data Remote Code Execution Vulnerability","id":"CVE-2026-0764","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":9.8,"headline":"GPT Academic: Pickle deserializing cookies may pose RCE risk","id":"CVE-2024-31224","kev_date_added":null,"published":"2024-04-08"},{"cvss_score":8.8,"headline":"Code Injection in binary-husky/gpt_academic","id":"CVE-2024-10950","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.8,"headline":"Prompt Injection Leading to RCE in binary-husky/gpt_academic Plugin `manim`","id":"CVE-2024-10954","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.8,"headline":"Local File Read (LFI) by Tarslip Symlink via arxiv_download() API in binary-husky/gpt_academic","id":"CVE-2024-10986","kev_date_added":null,"published":"2025-03-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["binary-husky"]},"summary":"Attackers can achieve remote command execution via pickle deserialization in the Latex error correction plugin of gpt_academic.","url":"https://insights.sbomify.com/CVE-2024-11039/"}