CVE-2026-40252
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 · uneditedFastGPT is an AI Agent building platform. Prior to 4.14.10.4, Broken Access Control vulnerability (IDOR/BOLA) allows any authenticated team to access and execute applications belonging to other teams by supplying a foreign appId. While the API correctly validates the team token, it does not verify that the requested application belongs to the authenticated team. This leads to cross-tenant data exposure and unauthorized execution of private AI workflows. This vulnerability is fixed in 4.14.10.4.
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 confidenceFastGPT prior to 4.14.10.4 contains an IDOR/BOLA vulnerability where the API validates team authentication tokens but fails to verify that the requested application (appId) belongs to the authenticated team. This allows any authenticated team to access and execute applications owned by other teams, resulting in cross-tenant data exposure and unauthorized workflow execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.14.10.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FastGPT versionLocate the running FastGPT version from the deployment (Docker image tag, package.json version field, or API health endpoint that exposes version info). Compare it against 4.14.10.4.Affected if Installed version is below 4.14.10.4
-
Confirm API authentication mechanismVerify that the FastGPT API accepts team authentication tokens (via header or cookie) for application access endpoints.Affected if API uses team-based authentication tokens without per-request ownership validation
-
Test cross-tenant appId accessUsing valid team credentials, submit an API request to access an application (appId parameter) that belongs to a different team. Observe whether the API returns the application data or allows execution.Affected if API returns data or executes workflows for appId values belonging to other teams without returning a 403 or ownership error
A FastGPT installation is affected if its version is below 4.14.10.4 and the API permits authenticated team users to access or execute applications (appId) owned by other teams.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.14.10.4
Upgrade FastGPT to version 4.14.10.4 or later. If immediate upgrade is not possible, implement application-ownership validation checks before processing any appId requests to ensure the authenticated team owns the requested resource.
4.14.10.4
- 1. Back up your current FastGPT installation and all associated data before proceeding with the upgrade.
- 2. Upgrade FastGPT to version 4.14.10.4 or later by following the standard upgrade procedure for your deployment method.
- 3. After upgrade, verify that the access control fix is working by testing that team A cannot access team B's applications using a foreign appId.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40252 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40252 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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