Authorization Flaw in FastGPT (CVE-2026-61644)
Summary
Vulnerability in FastGPT (CVE-2026-61644). Confidential information can be exposed externally. Exploitable via POST /api/core/chat/record/getCollectionQuote.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61644 has been found in FastGPT.
Attackers can target a specific entry point like POST /api/core/chat/record/getCollectionQuote over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "FastGPT CVE-2026-61644" on the vendor's site.
CVE-2026-61644 (FastGPT) — CWE-863 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/core/chat/record/getCollectionQuote
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in FastGPT. Attackers reach the vulnerable code path via POST /api/core/chat/record/getCollectionQuote.
Check the vendor advisory for the affected versions of FastGPT. Attack surface: POST /api/core/chat/record/getCollectionQuote.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/core/chat/record/getCollectionQuote requests with malformed payloads or SQL meta-characters. Run grep -r 'FastGPT' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'FastGPT' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
FastGPTを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/core/chat/record/getCollectionQuote' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/core/chat/record/getCollectionQuoteへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/core/chat/record/getCollectionQuote on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com