CVE-2026-61643

FastGPT: workflow runtime can execute another user's private HTTP toolset

Published Jul 15, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
FastGPT is a knowledge-based AI application platform. From 4.14.17 until 4.15.0-beta5, an authenticated FastGPT user can save a workflow node that points to another user's private HTTP toolset by using a crafted saved tool id such as http-<victim_toolset_app_id>/<tool_name>. The normal toolset routes deny access, but the workflow save and runtime path did not apply the same authorization check to the referenced toolset, allowing /api/v2/chat/completions to resolve the saved reference and execute the victim-owned HTTP tool. This issue is fixed in version 4.15.0-beta5.

Analysis

AI-generated

Technical impact

An authenticated FastGPT user can craft a saved workflow that points to another user's private HTTP toolset via a specially constructed tool ID. This flaw is a CWE-863 weakness that arises from an improper authorization check during workflow save and execution. The platform's toolset routes normally prevent unauthorized access, but the workflow save repeats the authorization check. When the user triggers the workflow through /api/v2/chat/completions, the reference resolves and the victim-owned HTTP tool is executed, allowing the attacker to run arbitrary requests against the victim's toolset infrastructure. This flaw enables the attacker to bypass access controls and potentially exfiltrate data or invoke privileged operations without the victim's consent.

Affected Systems

The vulnerability affects labring:FastGPT version 4.14.17 up to, but not including, 4.15.0-beta5. Versions prior to 4.14.17 or 4.15.0-beta5 and later are not affected.

Risk and Exploitability

The CVSS score is 5.9, indicating moderate severity, and the EPSS score is below 1%, suggesting a low probability that this weakness will be actively exploited. It is not listed in the CISA KEV catalog. The attack requires a legitimate authenticated account to create or alter a workflow referencing a private toolset; the execution occurs during normal workflow runtime. Because the flaw is limited to authenticated users and does not involve remote network entry, the overall risk is moderate but present for existing installations not yet patched.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor‑released update to FastGPT v4.15.0‑beta5 or later.
  • Audit existing workflows for references to other users’ private HTTP toolsets and remove or delete any offending nodes.
  • Restrict privileged workflow configuration permissions so that only authorized users can reference external tool IDs, and enforce the proper authorization check on workflow save and run endpoints.

Generated by OpenCVE AI on August 3, 2026 at 03:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Labring
Labring fastgpt
Vendors & Products Labring
Labring fastgpt
Type Values Removed Values Added
Description FastGPT is a knowledge-based AI application platform. From 4.14.17 until 4.15.0-beta5, an authenticated FastGPT user can save a workflow node that points to another user's private HTTP toolset by using a crafted saved tool id such as http-<victim_toolset_app_id>/<tool_name>. The normal toolset routes deny access, but the workflow save and runtime path did not apply the same authorization check to the referenced toolset, allowing /api/v2/chat/completions to resolve the saved reference and execute the victim-owned HTTP tool. This issue is fixed in version 4.15.0-beta5.
Title FastGPT: workflow runtime can execute another user's private HTTP toolset
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 20, 2026, 2:32 PM
Reserved
Jul 10, 2026, 5:38 PM
Status
Deferred
Published
Jul 15, 2026, 6:16 PM
Modified
Oct 24, 2026, 9:10 PM