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

CVE-2026-61646

MEDIUM · 6.3 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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 a knowledge-based AI application platform. Prior to 4.15.0-beta5, FastGPT's shared SSRF guard validates only the initial request URL before handing the request to axios, and axios follows redirects by default. An authenticated workflow user can configure an HTTP request node to call an attacker-controlled public URL that redirects to cloud metadata, loopback, or internal services that the guard would block on direct request, and the HTTP node returns the response body to the workflow caller. This issue is fixed in version 4.15.0-beta5.

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 shared SSRF guard validates only the initial request URL before handing to axios, but axios follows redirects by default. An authenticated workflow user can configure an HTTP request node to call a malicious public URL that redirects to cloud metadata, loopback, or internal services that the guard would normally block, allowing the HTTP node to return the response body to the workflow caller.

MitigationUpgrade to FastGPT version 4.15.0-beta5 or later which implements proper redirect following and validation in the SSRF guard.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 directory or check running containers/processes for the FastGPT application. Look for package.json or docker-compose files containing 'fastgpt'.
    Affected if FastGPT is present in the environment
  2. Determine FastGPT version
    Check the installed version by examining package.json, a docker image tag, or running 'git describe --tags' in the project directory. Compare against the fixed version 4.15.0-beta5.
    Affected if Version is earlier than 4.15.0-beta5 (e.g., 4.14.x, 4.15.0-beta4 or earlier)
  3. Verify HTTP request node is enabled
    Check if the workflow feature with HTTP request node capability is accessible to authenticated users. Review user role permissions or workflow configuration files.
    Affected if Authenticated users can access and configure HTTP request nodes in workflows
  4. Confirm SSRF guard exists but validates only initial URL
    Examine the source code or configuration of the SSRF guard module. Look for validation logic that checks only the initial URL parameter before passing to axios, without inspecting redirect destinations.
    Affected if SSRF guard validates initial URL only and does not intercept axios redirects
  5. Check axios redirect behavior
    Inspect axios configuration in the HTTP request node implementation. Verify that 'maxRedirects' is not set to 0 or that redirect targets are not validated before following.
    Affected if Axios is configured to follow redirects by default without validation

Environment is affected if FastGPT version is earlier than 4.15.0-beta5, HTTP request nodes are accessible to authenticated users, and the SSRF guard does not validate redirect destinations.

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 to FastGPT version 4.15.0-beta5 or later which implements proper redirect following and validation in the SSRF guard.

Recommended fix High confidence

4.15.0-beta5

  1. Upgrade FastGPT to version 4.15.0-beta5 or later to receive the SSRF guard fix
  2. After upgrading, verify that the HTTP request node properly blocks redirects to cloud metadata, loopback, and internal services
  3. Confirm that the SSRF guard now validates the final redirect destination rather than just the initial URL
Caveat This is a beta version upgrade; review release notes for any potential breaking changes before deploying to production

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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