dbcve.org
FastgptApplication

CVE-2025-62612

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-22
Fix available
A fix is available. Upgrade to 4.11.1 or later.
See remediation →
62/100
Remediation priority · Elevated
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
FastGPT is an AI Agent building platform. Prior to version 4.11.1, in the workflow file reading node, the network link is not security-verified, posing a risk of SSRF attacks. This issue has been patched in version 4.11.1.

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

FastGPT versions prior to 4.11.1 contain an SSRF vulnerability in the workflow file reading node. The node processes network links (URLs) without proper security validation, allowing an attacker to induce the server to make arbitrary network requests to internal services or external systems.

MitigationUpgrade FastGPT to version 4.11.1 or later. If immediate upgrade is not possible, restrict network access to the FastGPT server and disable or firewall the workflow file reading node until the patch can be applied.

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.11.1

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 version
    Check the FastGPT version running in your environment. This is typically visible in the admin panel, container image tag, or deployment configuration. Compare it against the fixed version 4.11.1.
    Affected if The installed version is lower than 4.11.1
  2. Locate the workflow file reading node
    Access the FastGPT workflow editor and navigate to the nodes palette. Look for a node named 'File Reading', 'URL Reading', or similar that handles network links/URLs as input.
    Affected if The workflow file reading node exists and is available in the version
  3. Identify workflows using the node with URLs
    Review all active workflows in the system. Check if any workflow instances utilize the file reading node with HTTP/HTTPS URLs as input sources.
    Affected if Any workflow passes external or internal URLs through the file reading node
  4. Check network exposure
    Determine whether the FastGPT server has network access to internal services, cloud metadata endpoints, or other sensitive internal resources that could be targeted via SSRF.
    Affected if The FastGPT server can initiate outbound network requests to internal infrastructure

You are affected if FastGPT version is below 4.11.1 AND the workflow file reading node is actively used with network URLs, especially in environments where the server can reach internal services.

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.11.1 or later
Fixed in 4.11.1
Interim mitigation

Upgrade FastGPT to version 4.11.1 or later. If immediate upgrade is not possible, restrict network access to the FastGPT server and disable or firewall the workflow file reading node until the patch can be applied.

Recommended fix High confidence

FastGPT version 4.11.1

  1. Identify the current FastGPT version in use by checking the deployment configuration or running 'docker images' or checking the package.json
  2. Stop any running FastGPT instances to prevent during-update access
  3. Upgrade FastGPT to version 4.11.1 or later. If using Docker, update the image tag: 'docker pull fastgpt/fastgpt:4.11.1' and recreate the container
  4. If using a package installation, run the appropriate package manager command to upgrade to 4.11.1
  5. Verify the upgrade was successful by checking the FastGPT version after startup
  6. Test the workflow file reading node functionality to ensure it still works correctly after 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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