dbcve.org
Gpt AcademicApplication · Binary Husky

CVE-2026-0763

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 run_in_subprocess_wrapper_func 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 run_in_subprocess_wrapper_func function. 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-27958.

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 · high confidence

GPT Academic contains a deserialization vulnerability in the run_in_subprocess_wrapper_func function. The function fails to validate user-supplied data before deserialization, allowing unauthenticated remote attackers to execute arbitrary code as root.

MitigationImplement proper input validation and avoid deserializing untrusted data; replace unsafe deserialization with safer alternatives such as JSON or validated serialization formats.

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. Locate GPT Academic installation and version
    Search for GPT Academic installation directories (e.g., /usr/local/GPT_Academic, ~/GPT_Academic, or similar paths) and check for version file or binary version info
    Affected if GPT Academic version 3.91 is installed and the run_in_subprocess_wrapper_func module exists in the installation
  2. Verify exact version number
    Run 'git describe --tags' in the installation directory, check version.py, or inspect the binary metadata for version 3.91
    Affected if Installed version is exactly 3.91 (Binary Husky Gpt Academic)
  3. Check if run_in_subprocess_wrapper_func is exposed
    Search the codebase for the run_in_subprocess_wrapper_func function definition and determine if it is exposed via API endpoints, web routes, or network services
    Affected if The function is exposed via HTTP/HTTPS API or other network-accessible interface without authentication
  4. Identify deserialization usage in vulnerable function
    Inspect the run_in_subprocess_wrapper_func source code for pickle.loads, marshal.load, or other unsafe deserialization calls on user-supplied data
    Affected if The function uses pickle, marshal, or similar unsafe deserialization methods without input validation on user-provided data
  5. Check network accessibility of vulnerable endpoint
    Review web server configuration and firewall rules to determine if the endpoint containing run_in_subprocess_wrapper_func is reachable from network
    Affected if The vulnerable function is reachable over network without authentication

A user is affected if GPT Academic version 3.91 is installed and the run_in_subprocess_wrapper_func is exposed via a network-accessible interface without authentication.

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

Implement proper input validation and avoid deserializing untrusted data; replace unsafe deserialization with safer alternatives such as JSON or validated serialization formats.

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-0763 — 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-0763 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