# CVE-2026-34162: FastGPT: Unauthenticated SSRF via httpTools Endpoint Leads to Internal API Key Theft

> Unauthenticated attackers can exploit an exposed HTTP proxy endpoint to perform Server-Side Request Forgery and steal internal API keys.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2026
- **Updated:** 31 Mar 2026
- **Also known as:** GHSA-w36r-f268-pwrj

## What is CVE-2026-34162?

CVE-2026-34162 is a critical server-side request forgery vulnerability in labring FastGPT, published on 31 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FastGPT 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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-34162?

It affects 1 product.


Products: Fastgpt Fastgpt.

## How do I fix CVE-2026-34162?

No fix has been published for CVE-2026-34162 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-34162 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34162 exists.

## Other vulnerabilities in labring FastGPT

- [CVE-2026-40351](https://insights.sbomify.com/CVE-2026-40351/): FastGPT: NoSQL Injection in loginByPassword leads to Authentication Bypass (critical 9.8)
- [CVE-2026-33075](https://insights.sbomify.com/CVE-2026-33075/): FastGPT has Arbitrary Code Execution in GitHub Actions via pull_request_target in fastgpt-preview-image.yml (critical 9.4)
- [CVE-2026-40352](https://insights.sbomify.com/CVE-2026-40352/): FastGPT: NoSQL Injection in updatePasswordByOld Leads to Account Takeover (high 8.8)
- [CVE-2026-34163](https://insights.sbomify.com/CVE-2026-34163/): Server-Side Request Forgery via MCP Tools Endpoint in FastGPT (high 7.7)
- [CVE-2026-26075](https://insights.sbomify.com/CVE-2026-26075/): Cross-Site Request Forgery (CSRF) in FastGPT (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34162 and fix it if it is affected.

What it is: CVE-2026-34162 is a critical server-side request forgery vulnerability in labring FastGPT, published on 31 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34162 exists.

Affected product: labring FastGPT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34162/ (Markdown: https://insights.sbomify.com/CVE-2026-34162/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34162
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34162
- OSV: https://osv.dev/vulnerability/CVE-2026-34162

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34162/
Summaries are generated and may contain mistakes; the official description above is the record.