CVE-2024-12390: binary-husky/gpt_academic · Improper Link Resolution Before File Access
Affects binary-husky/gpt_academicSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-12390 effectively, European organizations should implement the following specific measures: 1) Immediately restrict or disable the processing of RAR archives from untrusted or unauthenticated sources within binary-husky/gpt_academic. 2) Implement strict validation of archive contents before extraction, including checking for symbolic links and disallowing their extraction or rewriting symlinks to safe locations. 3) Employ sandboxing or containerization techniques to isolate the extraction process, limiting the impact of any arbitrary file writes. 4) Monitor file system changes, especially in sensitive directories such as those containing SSH keys, crontabs, and application code, using file integrity monitoring tools. 5) Apply principle of least privilege to the application’s execution environment, ensuring it cannot write to critical system paths. 6) Stay alert for official patches or updates from the vendor and apply them promptly once available. 7) Educate developers and system administrators about the risks of extracting archives with symbolic links and encourage secure coding and deployment practices. 8) Consider alternative archive formats or extraction libraries that do not support symlinks or have better security controls. These targeted actions go beyond generic advice and address the specific exploitation vector of this vulnerability.
Description
A vulnerability in binary-husky/gpt_academic version git 310122f allows for remote code execution. The application supports the extraction of user-provided RAR files without proper validation. The Python rarfile module, which supports symlinks, can be exploited to perform arbitrary file writes. This can lead to remote code execution by writing to sensitive files such as SSH keys, crontab files, or the application's own code.