EUVD-2026-42117Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Authenticated low-privilege user (PR:L) reads other tenants' data over the network with no UI; confidentiality-only impact, no integrity/availability effect and unchanged scope.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
FastGPT is a knowledge-based AI application platform. Prior to 4.15.0, GET /api/core/ai/record/getRecord authenticates the caller but loads LLM request and response traces only by requestId without team scoping, allowing any authenticated user to read another team's prompts, retrieved RAG chunks, and completions if the requestId is known. This issue is fixed in version 4.15.0.
AnalysisAI
Broken object-level authorization in FastGPT before 4.15.0 lets any authenticated user retrieve another team's LLM interaction traces via GET /api/core/ai/record/getRecord. The endpoint verifies the caller is logged in but fetches records solely by requestId without checking team ownership, exposing cross-tenant prompts, retrieved RAG chunks, and model completions to any user who can guess or obtain a valid requestId. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV, but exploitation requires only a low-privilege account and knowledge of a target requestId.
Technical ContextAI
FastGPT is an open-source, knowledge-based AI/RAG application platform (vendor: labring, CPE cpe:2.3:a:labring:fastgpt) that orchestrates LLM calls and logs request/response traces for observability and debugging. The flaw is CWE-639 (Authorization Bypass Through User-Controlled Key), a classic Insecure Direct Object Reference: the getRecord handler treats the client-supplied requestId as a trusted lookup key and returns the matching trace without scoping the query to the requesting user's team/tenant. In a multi-tenant SaaS or shared-deployment model, the missing team-scoping predicate on the data query is the root cause - authentication is enforced but authorization (tenant isolation) is not.
RemediationAI
Vendor-released patch: upgrade to FastGPT 4.15.0 or later, which adds team scoping to the record lookup (fixing commit 60c62b7af8269c826885b541bb56e6e5c424c11a; advisory GHSA-6vx6-f72r-74cg). If an immediate upgrade is not possible, apply compensating controls: restrict or block external access to the /api/core/ai/record/getRecord endpoint at a reverse proxy or API gateway so only trusted internal callers reach it (trade-off: breaks any legitimate client that relies on trace retrieval), and in single-tenant deployments limit account provisioning to trusted users to shrink the pool of potential attackers. Where feasible, add a gateway-level authorization check tying the session's team to the requested record, though this duplicates logic the patch already provides and is best treated as interim only. Review access logs for anomalous getRecord calls enumerating requestIds to detect prior abuse.
FastGPT is an AI Agent building platform. Prior to version 4.9.12, the LastRoute Parameter on login page is vulnerable t
Unauthenticated HTTP proxy abuse in FastGPT (AI Agent platform) prior to v4.14.9.5 allows remote attackers to relay arbi
Remote code execution in FastGPT's agent-sandbox component (versions 4.14.10 through 4.14.12) lets any network-adjacent,
NoSQL injection in FastGPT <4.14.9.5 password authentication allows unauthenticated remote attackers to bypass login con
Channel hijack and denial of service in FastGPT (labring/FastGPT) before 4.15.2 lets an unauthenticated remote attacker
GitHub Actions artifact-poisoning (pwn request) in labring/FastGPT allows an external attacker who opens a pull request
NoSQL injection in FastGPT versions before 4.14.9.5 allows authenticated attackers to bypass password verification on th
FastGPT versions 4.14.8.3 and below contain a critical arbitrary code execution vulnerability in the fastgpt-preview-ima
Authentication bypass in FastGPT 4.15.0-beta4 lets unauthenticated remote attackers forge JWTs and access internal plugi
Cross-tenant file disclosure in FastGPT prior to v4.15.0-beta5 allows an attacker to read another team's stored files by
Server-side request forgery in FastGPT before 4.15.0-beta4 lets an authenticated team member abuse the HTTP-tool OpenAPI
Server-Side Request Forgery in Labring FastGPT prior to 4.15.0-beta1 lets an authenticated attacker bypass the platform'
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today