CVE-2026-34162
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 version 4.14.9.5, the FastGPT HTTP tools testing endpoint (/api/core/app/httpTools/runTool) is exposed without any authentication. This endpoint acts as a full HTTP proxy — it accepts a user-supplied baseUrl, toolPath, HTTP method, custom headers, and body, then makes a server-side HTTP request and returns the complete response to the caller. This issue has been patched in version 4.14.9.5.
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 versions before 4.14.9.5 expose the /api/core/app/httpTools/runTool endpoint without authentication. This endpoint functions as a full HTTP proxy, accepting user-supplied baseUrl, toolPath, HTTP method, headers, and body to make server-side requests and return complete responses. The vulnerability enables unauthenticated attackers to use the server as a proxy for arbitrary HTTP requests, facilitating SSRF attacks against internal services, cloud metadata endpoints, and internal network resources.
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.9.5CVSS 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 your FastGPT installation versionCheck the version number running in your environment. This is typically visible in the application UI, startup logs, container tags, or deployment manifests. Compare this version against the affected range: versions prior to 4.14.9.5.Affected if The installed FastGPT version is lower than 4.14.9.5
-
Locate the vulnerable HTTP tools endpointVerify that the endpoint /api/core/app/httpTools/runTool exists in your FastGPT deployment. This is typically found in the API routes or service documentation.Affected if The endpoint /api/core/app/httpTools/runTool is present in your environment
-
Confirm the endpoint lacks authenticationAttempt to access the /api/core/app/httpTools/runTool endpoint without providing valid authentication credentials (such as login tokens, API keys, or session cookies). Observe whether the request is accepted and processed.Affected if The endpoint accepts and processes requests without requiring any authentication tokens or authorization headers
-
Test if arbitrary URLs are acceptedSend a test request to the endpoint with user-controlled parameters: a baseUrl pointing to an internal or external address (such as http://localhost or a known internal service), a toolPath, HTTP method, headers, and body. Check if the server makes the request and returns the response.Affected if The endpoint accepts user-supplied baseUrl, toolPath, method, headers, and body parameters and returns the full response from the specified URL
You are affected if your FastGPT version is below 4.14.9.5 AND the /api/core/app/httpTools/runTool endpoint is accessible without authentication AND accepts arbitrary URL parameters.
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.9.5
Apply vendor patch version 4.14.9.5 or later to enforce authentication on the /api/core/app/httpTools/runTool endpoint. Until patched, network-level restrictions on the endpoint should be implemented as a compensating control.
4.14.9.5
- Upgrade FastGPT to version 4.14.9.5 or later to remediate the missing authentication vulnerability
- After upgrading, verify that the /api/core/app/httpTools/runTool endpoint now requires authentication
- Consult the FastGPT release notes or changelog to confirm the security patch was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34162 — 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-34162 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