dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-44285

HIGH · 7.7 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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
FastGPT is an AI Agent building platform. Prior to 4.15.0-beta1, a Server-Side Request Forgery (SSRF) vulnerability allows an authenticated attacker to bypass the global isInternalAddress network protection and make arbitrary HTTP GET requests to internal network services. This is achieved by exploiting an incomplete fix in the dataset preview endpoint /api/core/dataset/file/getPreviewChunks when utilizing the externalFile data import type. This vulnerability is fixed in 4.15.0-beta1.

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 versions prior to 4.15.0-beta1 contain an authenticated SSRF vulnerability in the dataset preview endpoint /api/core/dataset/file/getPreviewChunks. When using the externalFile data import type, attackers can bypass the isInternalAddress protection mechanism and send arbitrary HTTP GET requests to internal network services. The vulnerability stems from an incomplete prior fix.

MitigationUpgrade FastGPT to version 4.15.0-beta1 or later. Until then, restrict access to the affected endpoint to trusted users only and monitor for suspicious internal network requests.

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

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

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 FastGPT installation
    Locate the FastGPT application in your environment - common paths include /opt/fastgpt, /var/www/fastgpt, or check running containers with 'docker ps' for fastgpt images
    Affected if FastGPT is present in the environment
  2. Check installed FastGPT version
    Review package.json, docker image tags, or run 'docker exec <container> cat package.json | grep version' to find the exact version number
    Affected if The version is any version prior to 4.15.0-beta1 (e.g., 4.14.x, 4.13.x, earlier releases)
  3. Verify dataset file import functionality is enabled
    Check if the dataset feature module is active by reviewing FastGPT configuration files or admin panel settings for dataset management and file import capabilities
    Affected if Dataset file import functionality is enabled and accessible to authenticated users
  4. Confirm externalFile import type is available
    Inspect the API endpoint /api/core/dataset/file/getPreviewChunks or review the data import options in the FastGPT web interface to verify the externalFile import type exists
    Affected if The externalFile data import type is available as an import option
  5. Verify authentication is required for the vulnerable endpoint
    Test that requests to /api/core/dataset/file/getPreviewChunks require valid authentication tokens by attempting unauthenticated access
    Affected if The endpoint accepts authenticated requests (even though it should require stronger protection)
  6. Check if internal network access is possible from the application
    Review FastGPT network configuration and the isInternalAddress protection implementation in the codebase or container environment variables
    Affected if The application can make outbound HTTP requests and has access to internal network addresses

Your environment is affected if FastGPT is running a version prior to 4.15.0-beta1 with the dataset file import feature and externalFile import type enabled, allowing authenticated users to potentially reach internal services through the vulnerable endpoint.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade FastGPT to version 4.15.0-beta1 or later. Until then, restrict access to the affected endpoint to trusted users only and monitor for suspicious internal network requests.

Recommended fix High confidence

4.15.0-beta1

  1. 1. Identify the current FastGPT version in use
  2. 2. If the current version is before 4.15.0-beta1, plan for upgrade to 4.15.0-beta1 or later
  3. 3. Review FastGPT upgrade documentation for migration procedures
  4. 4. Perform a backup of the current installation before upgrading
  5. 5. Upgrade FastGPT to version 4.15.0-beta1 or the latest stable release that includes this fix
  6. 6. Verify the upgrade was successful and the /api/core/dataset/file/getPreviewChunks endpoint now properly validates against SSRF

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

Have this fixed 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-44285 — 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-44285 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