PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-61646 labring CVE debrief

An authenticated user can exploit a server-side request forgery (SSRF) vulnerability in FastGPT versions before 4.15.0-beta5 to access cloud metadata, loopback, or internal services that the SSRF guard would block on direct request. This vulnerability allows an attacker to bypass the SSRF guard's restrictions by configuring an HTTP request node to call an attacker-controlled public URL that redirects to sensitive services. The issue is particularly concerning for FastGPT deployments with untrusted workflows, as it could lead to unauthorized information disclosure.

Vendor
labring
Product
FastGPT
CVSS
MEDIUM 6.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-15
Original CVE updated
2026-10-24
Advisory published
2026-07-15
Advisory updated
2026-10-24

Who should care

Defenders responsible for FastGPT deployments, particularly those with untrusted workflows, should assess exposure and validate the configuration of HTTP request nodes. This includes reviewing the current workflow configurations, verifying the access controls in place, and ensuring that the SSRF guard is properly configured to prevent unauthorized access to sensitive services.

Why it matters

The SSRF vulnerability in FastGPT allows authenticated users to access sensitive internal services, cloud metadata, and loopback services, potentially leading to unauthorized information disclosure.

  • Authenticated users can access sensitive internal services
  • Cloud metadata may be exposed to authenticated users
  • Loopback services may be accessible to authenticated users
  • Internal services may be reachable through SSRF

Technical summary

The FastGPT platform's shared SSRF guard validates only the initial request URL before handing the request to axios, which 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. This issue allows the attacker to access sensitive internal services, potentially leading to unauthorized information disclosure. The vulnerability is fixed in version 4.15.0-beta5.

Defensive priority

Defenders should prioritize verifying exposure of FastGPT instances to untrusted workflows and validating the configuration of HTTP request nodes.

Recommended defensive actions

  • Verify exposure of FastGPT instances to untrusted workflows
  • Validate the configuration of HTTP request nodes
  • Update to version 4.15.0-beta5 or later
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the SSRF vulnerability in FastGPT versions before 4.15.0-beta5. The issue allows an authenticated workflow user to configure an HTTP request node to call an attacker-controlled public URL that redirects to cloud metadata, loopback, or internal services.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-61646 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-61646

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-61646 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-61646

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.