dbcve.org
Gpt AcademicApplication · Binary Husky

CVE-2026-0764

CRITICAL · 9.8 CVSS v3.0 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GPT Academic upload Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GPT Academic. Authentication is not required to exploit this vulnerability. The specific flaw exists within the upload endpoint. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-27957.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A critical deserialization vulnerability exists in the GPT Academic upload endpoint. The lack of proper validation on user-supplied data allows unauthenticated attackers to send malicious serialized objects that, when deserialized, execute arbitrary code with root privileges.

MitigationDisable unsafe deserialization mechanisms, implement strict input validation with allowlists for acceptable upload content types, and consider migrating to safer data formats like JSON. If deserialization is required, use safe libraries with enabled security checks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gpt AcademicApplication
Affected:= 3.91

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if GPT Academic is installed
    Look for the GPT Academic application on the system - typically installed in directories like /opt/gpt_academic, /home/user/gpt_academic, or check via package managers. Look for files named 'gpt_academic', 'GPT学术优化', or related executables.
    Affected if GPT Academic software is found on the system
  2. Verify the installed version is 3.91
    Run commands to check the version such as: gpt_academic --version, pip show gpt-academic, or check version files in the installation directory. Compare the exact version number to 3.91.
    Affected if The installed version is exactly 3.91
  3. Confirm the upload endpoint is exposed
    Check if the GPT Academic web service is running and accessible. Look for routes related to upload functionality in the application's URL patterns (e.g., /upload, /api/upload, /file/upload). Review the application's network configuration and firewall rules.
    Affected if The upload endpoint is accessible from the network or internet without authentication
  4. Check if deserialization is enabled for uploads
    Inspect the application source code for upload handling - look for pickle.load(), yaml.load(), json.loads() with unsafe settings, or similar deserialization functions processing user input. Check configuration files for settings related to data serialization or object handling.
    Affected if The application uses deserialization functions (pickle, yaml, etc.) to process uploaded data without strict type checking or allowlists

You are affected if GPT Academic version 3.91 is installed AND the upload endpoint is exposed AND the application uses unsafe deserialization to process uploaded content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable unsafe deserialization mechanisms, implement strict input validation with allowlists for acceptable upload content types, and consider migrating to safer data formats like JSON. If deserialization is required, use safe libraries with enabled security checks.

Fix this in Gpt Academic Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0764 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0764 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data