dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-61643

MEDIUM · 5.9 CVSS v3.1 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 →
65/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. 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.

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

An IDOR/broken access control vulnerability in FastGPT allows authenticated users to save workflow nodes referencing other users' private HTTP toolsets by using crafted tool IDs like 'http-<victim_toolset_app_id>/<tool_name>'. The workflow save/runtime path lacks the authorization checks that normal toolset routes properly enforce, enabling attackers to execute victim-owned HTTP tools via /api/v2/chat/completions.

MitigationUpgrade to FastGPT version 4.15.0-beta5 or later, which adds the missing authorization checks to the workflow save and runtime paths.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/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. Check FastGPT version
    Locate the installed FastGPT version (typically in package.json, Docker image tag, or admin panel). Compare it to 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)
  2. Identify workflow definitions with HTTP tool nodes
    Export or query workflow configurations from the database. Search for workflow nodes where 'toolType' or 'toolId' contains 'http-' followed by what appears to be another user's app ID pattern.
    Affected if Workflows contain HTTP tool node configurations with tool IDs matching pattern 'http-<app_id>/<tool_name>' where the app_id differs from the workflow owner's identifier
  3. Audit tool references in workflow save/runtime data
    Review API logs or database records for /api/v2/chat/completions requests where the 'tools' or 'tool_ids' parameter contains references to HTTP toolsets belonging to other users.
    Affected if Requests contain tool IDs referencing private toolsets not owned by the authenticated requester
  4. Check for unauthorized HTTP tool executions
    Review application logs or audit trails for executions of HTTP tools via /api/v2/chat/completions where the tool owner differs from the workflow or request owner.
    Affected if HTTP tool executions occur for toolsets where the authenticated user is not the owner

User is affected if running FastGPT version earlier than 4.15.0-beta5 and workflows or API requests contain HTTP tool references that access private toolsets belonging to other users.

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 adds the missing authorization checks to the workflow save and runtime paths.

Recommended fix Moderate confidence

4.15.0-beta5

  1. Identify the FastGPT installation and verify the current version is between 4.14.17 and 4.15.0-beta5
  2. Upgrade FastGPT to version 4.15.0-beta5 or later to apply the authorization fix for the workflow node vulnerability

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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