dbcve.org
Gpt AcademicApplication · Binary Husky

CVE-2026-0762

HIGH · 8.1 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 →
90/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 stream_daas Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GPT Academic. Interaction with a malicious DAAS server is required to exploit this vulnerability but attack vectors may vary depending on the implementation. The specific flaw exists within the stream_daas 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-27956.

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's stream_daas function contains a deserialization vulnerability where user-supplied data is deserialized without proper validation, allowing remote attackers to achieve RCE as root by interacting with a malicious DAAS server.

MitigationImplement strict input validation and use safe deserialization methods (e.g., avoid pickle, use json/binary formats with schema validation) before processing user-supplied data in the stream_daas function.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/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. Identify GPT Academic installation
    Locate the GPT Academic application directory or running process. Common indicators include directories named 'GPT-Academic', 'gpt_academic', or a Python project with 'gpt学术' in the name. Check running processes for 'gpt_academic' or similar.
    Affected if GPT Academic is installed and the application directory or process is found on the system
  2. Determine installed version
    Look for version information in the installation directory. Check files named 'version', '__version__', 'VERSION', or inspect the main Python package metadata using 'pip show gpt-academic' or examining the source code for version constants.
    Affected if The installed version matches 3.91 exactly (Binary Husky Gpt Academic: = 3.91)
  3. Locate stream_daas function
    Search the source code for the stream_daas function definition. Look in Python files within the project for 'def stream_daas' or 'stream_daas'. This function handles DAAS (Desktop as a Service) streaming.
    Affected if The stream_daas function exists in the codebase and is accessible to the application
  4. Check DAAS configuration exposure
    Examine configuration files or environment variables that control DAAS server connections. Look for settings related to 'DAAS', 'stream_daas', 'server_url', or remote service endpoints in config files, .env files, or command-line arguments.
    Affected if The application is configured to connect to or accept connections from external DAAS servers, enabling the deserialization attack surface
  5. Verify network exposure of DAAS endpoint
    Check if the stream_daas endpoint is exposed on the network. Review network listeners, reverse proxy configurations, or firewall rules that allow external access to DAAS-related routes. Look for routes containing 'daas' in the web server configuration.
    Affected if The stream_daas function is network-accessible without proper authentication or validation

A system is affected if GPT Academic version 3.91 is installed and the stream_daas function is enabled and network-accessible, allowing untrusted data to be deserialized.

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 strict input validation and use safe deserialization methods (e.g., avoid pickle, use json/binary formats with schema validation) before processing user-supplied data in the stream_daas function.

Fix this in Gpt Academic Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0762 — 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-0762 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