dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-42302

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-08
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
FastGPT is an AI Agent building platform. From version 4.14.10 to before version 4.14.13, the agent-sandbox component of FastGPT is vulnerable to unauthenticated Remote Code Execution (RCE). The startup script entrypoint.sh initializes code-server with the --auth none flag and binds the service to all network interfaces (0.0.0.0:8080). This configuration allows any user with network access to the port to bypass authentication and gain full control over the sandbox environment. This issue has been patched in version 4.14.13.

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

FastGPT's agent-sandbox component versions 4.14.10 through 4.14.12 have an unauthenticated RCE vulnerability. The startup script entrypoint.sh misconfigures code-server by disabling authentication (--auth none) and exposing the service on all network interfaces (0.0.0.0:8080), allowing any network attacker direct access to execute arbitrary code in the sandbox environment.

MitigationUpgrade to FastGPT version 4.14.13 or later which contains the patch. If immediate upgrade is not possible, implement network segmentation to restrict access to the sandbox port and enable authentication on code-server.

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

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.1/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. Identify if FastGPT agent-sandbox component is deployed
    Check running containers or processes for the agent-sandbox component. Look for code-server or related sandbox processes in your FastGPT deployment.
    Affected if The agent-sandbox component is present in the environment
  2. Verify code-server authentication configuration
    Inspect the sandbox container/process startup arguments or configuration files for the --auth none flag. Check command-line arguments or environment variables controlling code-server authentication.
    Affected if The --auth none flag is present, meaning authentication is disabled
  3. Confirm network binding address
    Inspect the network binding configuration for the sandbox service. Check process listening ports and binding addresses, specifically looking for 0.0.0.0:8080 binding.
    Affected if The service binds to 0.0.0.0 instead of localhost/127.0.0.1, exposing it to all network interfaces
  4. Check network accessibility of port 8080
    From an external host or non-localhost network segment, attempt to reach the sandbox port (e.g., curl http://target:8080 or telnet target 8080). Verify if the port is accessible from untrusted networks.
    Affected if Port 8080 is accessible from network locations other than localhost
  5. Compare installed FastGPT version to fixed release
    Check the installed FastGPT version against version 4.14.13, which contains the fix for this vulnerability.
    Affected if The installed version is earlier than 4.14.13 and the above exposure conditions exist

The environment is affected if FastGPT agent-sandbox is running with --auth none flag while bound to 0.0.0.0:8080, making the unauthenticated sandbox accessible from the network.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to FastGPT version 4.14.13 or later which contains the patch. If immediate upgrade is not possible, implement network segmentation to restrict access to the sandbox port and enable authentication on code-server.

Recommended fix High confidence

4.14.13

  1. Stop the FastGPT service to ensure no active connections during upgrade
  2. Upgrade FastGPT to version 4.14.13 or later using your deployment method (e.g., Docker image pull, helm upgrade, or package manager)
  3. Restart the FastGPT service after upgrade
  4. Verify the agent-sandbox component no longer exposes code-server with --auth none on 0.0.0.0:8080 by checking the entrypoint.sh script in the container

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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