Quick answers
- Is CVE-2026-34162 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34162 being exploited in the wild.
- How severe is CVE-2026-34162?
- Critical severity, with a CVSS score of 10, published 31 March 2026.
- Which products and versions are affected?
- labring FastGPT < 4.14.9.5.
- Is there a fix for CVE-2026-34162?
- A patch was published on 2026-03-25: Fix merged in pull request #6640 and released in v4.14.9.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34162 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-34162?
- Check whether you run Fastgpt. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The FastGPT HTTP tools testing endpoint (/api/core/app/httpTools/runTool) was exposed without any authentication middleware. This endpoint functions as a full HTTP proxy, accepting user-supplied parameters including baseUrl, toolPath, HTTP method, custom headers, and body. Because FastGPT is commonly deployed via Docker Compose, an unauthenticated remote attacker can use this endpoint to perform Server-Side Request Forgery (SSRF) against internal services. This allows for the exfiltration of third-party API keys from the AI Proxy management API, retrieval of MongoDB diagnostic data, and access to internal verification codes. The vulnerability has been addressed in version 4.14.9.5 by enforcing authentication and implementing internal address checks.
Affected products
- labring FastGPT < 4.14.9.5
Timeline
- 2026-03-25: patched: Fix merged in pull request #6640 and released in v4.14.9.5
- 2026-03-26: advisory: GitHub Security Advisory GHSA-w36r-f268-pwrj published
- 2026-03-31: disclosed: CVE-2026-34162 published to NVD