CVE-2026-61646
Deferred Deferred - Pending Action

SSRF via Redirect in FastGPT Prior to 4.15.0-beta5

Publication date: 2026-07-15

Last updated on: 2026-07-15

Assigner: GitHub, Inc.

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-15
Last Modified
2026-07-15
Generated
2026-08-04
AI Q&A
2026-07-15
EPSS Evaluated
2026-08-03
NVD
CVE-2026-61646
EUVD
EUVD-2026-44678

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
labring fastgpt to 4.15.0-beta5 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in FastGPT versions before 4.15.0. The shared SSRF guard only checks the initial URL before passing the request to axios, which follows redirects by default. Attackers can exploit this by setting up a URL that redirects to internal or cloud metadata services, bypassing the guard's protection. The HTTP node then returns the response from the blocked target to the workflow caller.

Detection Guidance

To detect this SSRF vulnerability in FastGPT, monitor network traffic for HTTP requests originating from FastGPT workflows that redirect to internal or cloud metadata endpoints. Check logs for requests to URLs like 169.254.169.254 or localhost after an initial external URL. Use tools like tcpdump or Wireshark to capture outbound traffic from FastGPT servers and inspect for suspicious redirect patterns.

Impact Analysis

An attacker with authenticated access could access sensitive internal services like cloud metadata endpoints or localhost, potentially exposing confidential data. The attacker could retrieve metadata, configuration details, or other sensitive information from internal systems through the workflow HTTP node.

Compliance Impact

This SSRF vulnerability could lead to unauthorized access to internal systems, potentially exposing personal or sensitive data. This may violate compliance requirements under GDPR (data protection) and HIPAA (health information privacy), as unauthorized data exposure could result in regulatory penalties and loss of trust.

Mitigation Strategies

Upgrade FastGPT to version 4.15.0-beta5 or later to apply the fix. If upgrading is not immediately possible, disable HTTP request node redirects in the SSRF guard configuration or implement redirect validation to block requests that redirect to internal or cloud metadata endpoints. Restrict network access to sensitive internal services as an additional precaution.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-61646. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart