dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-61644

HIGH · 7.7 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 →
83/100
Remediation priority · High
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, the POST /api/core/chat/record/getCollectionQuote endpoint authenticates the caller's chat and collection context, but the initialId center-node lookup is not bound to that authorized context. A low-privileged tenant user can call the endpoint with valid attacker-owned appId, chatId, chatItemDataId, and collectionId values while supplying another tenant's dataset data id as initialId, causing the response to include foreign dataset quote or full-text content. 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

The POST /api/core/chat/record/getCollectionQuote endpoint authenticates the overall chat and collection context but fails to bind the initialId parameter (used for center-node lookup) to that authorized tenant context. A low-privileged tenant can supply their own valid appId, chatId, chatItemDataId, and collectionId while using another tenant's dataset data ID as initialId, causing the response to leak foreign tenant dataset quotes or full-text content.

MitigationUpgrade to FastGPT version 4.15.0-beta5 or later, which properly binds the initialId lookup to the authorized tenant context.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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. Identify FastGPT version
    Check the installed FastGPT version by reviewing the deployment configuration, container image tag, or package.json file. Common locations: docker-compose.yml, Helm values.yaml, or the application's package.json in the deployment artifacts.
    Affected if The installed version is earlier than 4.15.0-beta5 (versions 4.15.0-beta4 and earlier are affected).
  2. Confirm multi-tenancy is enabled
    Review the FastGPT configuration file (config.yaml or environment variables) for multi-tenant settings. Look for tenant-related configuration keys or multi-tenant mode flags that enable tenant isolation.
    Affected if Multi-tenancy is enabled and the system handles sensitive data across tenants, making the tenant isolation bypass applicable.
  3. Verify endpoint accessibility
    Check if the POST /api/core/chat/record/getCollectionQuote endpoint is exposed in the deployed API. This can be confirmed by reviewing API routing configuration or testing endpoint availability.
    Affected if The endpoint is publicly or internally accessible without additional access controls beyond basic authentication.
  4. Review API access logs for the vulnerable endpoint
    Search application logs for requests to /api/core/chat/record/getCollectionQuote. Look for instances where initialId values differ from the authenticated tenant's dataset IDs, indicating potential exploitation.
    Affected if Logs show requests with initialId values that reference dataset IDs outside the requester's apparent tenant scope.

A user is affected if their FastGPT deployment runs version 4.15.0-beta4 or earlier with multi-tenancy enabled and the vulnerable endpoint is accessible to low-privileged tenant 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 properly binds the initialId lookup to the authorized tenant context.

Recommended fix High confidence

4.15.0-beta5

  1. Identify the currently deployed FastGPT version using deployment configuration or admin interface
  2. If running version 4.14.17 through 4.15.0-beta4, plan for upgrade to version 4.15.0-beta5
  3. Backup the current deployment configuration and any persistent data
  4. Upgrade FastGPT to version 4.15.0-beta5 following the project's standard upgrade procedure
  5. Verify the upgrade was successful by checking the version number in the admin interface
  6. Test that the /api/core/chat/record/getCollectionQuote endpoint now correctly enforces authorization bounds on the initialId parameter
  7. Confirm that low-privileged tenant users can no longer access other tenants' dataset content via this endpoint
Caveat beta releases may contain untested features; consider waiting for stable 4.15.0 if available

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
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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