dbcve.org
FastgptApplication

CVE-2026-26075

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-12
Fix available
A fix is available. Upgrade to 4.14.7 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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. Due to the fact that FastGPT's web page acquisition nodes, HTTP nodes, etc. need to initiate data acquisition requests from the server, there are certain security issues. In addition to implementing internal network isolation in the deployment environment, this optimization has added stricter internal network address detection. This vulnerability is fixed in 4.14.7.

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 web page acquisition and HTTP nodes allow the server to make arbitrary HTTP requests based on user input without proper validation. This creates a Server-Side Request Forgery (SSRF) vulnerability that can be exploited to access internal network resources, metadata endpoints, or internal services. The fix adds stricter internal network address detection to prevent requests to private/internal IP ranges.

MitigationUpdate to FastGPT version 4.14.7 or later. Additionally, implement internal network isolation in the deployment environment as a defense-in-depth measure.

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
FastgptApplication
Affected:< 4.14.7

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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. Check FastGPT version
    Locate the running FastGPT version number in your deployment (check Docker container tags, Helm chart version, package.json version field, or the application's about/settings page). Compare this version against the affected range: versions below 4.14.7 are vulnerable.
    Affected if The installed version is below 4.14.7
  2. Identify use of HTTP node or web page acquisition feature
    Review your FastGPT workflows and configurations to determine if the HTTP request node or the web page content acquisition feature is actively used or exposed to users. Check workflow definitions for nodes that perform arbitrary HTTP requests based on user-provided URLs.
    Affected if HTTP nodes or web page acquisition functionality is enabled and accessible to users without additional network restrictions
  3. Verify network-level internal address filtering
    Inspect your deployment environment's network configuration (firewall rules, Kubernetes network policies, or proxy configuration) to determine if outbound HTTP requests can reach private/internal IP ranges (e.g., 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 127.0.0.1, cloud metadata endpoints).
    Affected if The deployment environment allows HTTP requests from FastGPT to internal/private IP addresses without additional filtering

You are affected if running FastGPT version below 4.14.7 AND using the HTTP node or web page acquisition feature without compensating network controls that block requests to internal/private IP ranges.

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
Upgrade available Upgrade to 4.14.7 or later
Fixed in 4.14.7
Interim mitigation

Update to FastGPT version 4.14.7 or later. Additionally, implement internal network isolation in the deployment environment as a defense-in-depth measure.

Recommended fix High confidence

Upgrade to FastGPT version 4.14.7

  1. 1. Back up your current FastGPT configuration and data directory to prevent data loss during upgrade.
  2. 2. Stop the currently running FastGPT instance.
  3. 3. If using Docker, update your Docker image to version 4.14.7 by pulling the latest image: `docker pull fastgpt/fastgpt:4.14.7`
  4. 4. If using Docker Compose, update the image tag in your docker-compose.yml file to version 4.14.7 and recreate containers: `docker-compose up -d`
  5. 5. If using Kubernetes or other deployment methods, update the deployment configuration to use version 4.14.7 and apply the changes.
  6. 6. Verify the upgrade was successful by checking the FastGPT version in the admin interface or via API.
  7. 7. Test that the web page acquisition nodes and HTTP nodes function correctly after the upgrade.
  8. 8. Confirm internal network address detection is working as expected per the security fix.

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

Fix this in Fastgpt Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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