{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25185 exists.","fix":"No fix has been published for CVE-2025-25185 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25185 is a high-severity path traversal vulnerability in binary-husky gpt_academic, published on 3 Mar 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-25185 and fix it if it is affected.\n\nWhat it is: CVE-2025-25185 is a high-severity path traversal vulnerability in binary-husky gpt_academic, published on 3 Mar 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-25185 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-2025-25185/ (Markdown: https://insights.sbomify.com/CVE-2025-25185/index.md)","id":"CVE-2025-25185","markdown":"https://insights.sbomify.com/CVE-2025-25185/index.md","name":"CVE-2025-25185","record":{"aliases":["GHSA-gqp5-wm97-qxcv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GPT Academic","requires_auth":"none","summary":"Attackers can read arbitrary server files by uploading a malicious tar.gz containing symlinks, exposing sensitive data on the GPT Academic server.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gpt_academic","vendor":"binary-husky"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"GPT Academic provides interactive interfaces for large language models. In 3.91 and earlier, GPT Academic does not properly account for soft links. An attacker can create a malicious file as a soft link pointing to a target file, then package this soft link file into a tar.gz file and upload it. Subsequently, when accessing the decompressed file from the server, the soft link will point to the target file on the victim server. The vulnerability allows attackers to read all files on the server.","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":"GPT Academic allows arbitary file read by tarfile uncompress within softlink","id":"CVE-2025-25185","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Net::IMAP vulnerable to possible DoS by memory exhaustion","id":"CVE-2025-25186"},"packages":[],"prev":{"headline":"Possible Log Injection in Rack::CommonLogger","id":"CVE-2025-25184"},"products":["gpt_academic"],"published":"2025-03-03","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"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in binary-husky/gpt_academic","id":"CVE-2024-11039","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-03","vendors":["binary-husky"]},"summary":"Attackers can read arbitrary server files by uploading a malicious tar.gz containing symlinks, exposing sensitive data on the GPT Academic server.","url":"https://insights.sbomify.com/CVE-2025-25185/"}