What is the CVSS score of EUVD-2026-17445?

EUVD-2026-17445 has a CVSS 3.1 base score of 10.0 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.1%.

Which versions of Fastgpt are affected by EUVD-2026-17445?

FastGPT versions prior to 4.14.9.5 contain an unauthenticated HTTP proxy vulnerability that allows attackers to relay arbitrary requests through your server, enabling internal network reconnaissance,…. A patch is available.

How to fix or mitigate EUVD-2026-17445?

Within 24 hours: Identify all FastGPT instances and verify versions (confirm if running <4.14.9.5). Within 7 days: Upgrade all instances to FastGPT v4.14.9.5 or later; test in staging environment before production deployment. Within 30 days: Review network logs for suspicious requests to /api/core/app/httpTools/runTool endpoint and conduct forensic analysis for unauthorized proxy activity; implement network segmentation to restrict outbound connections from FastGPT servers.

Fastgpt EUVD-2026-17445

| CVE-2026-34162 CRITICAL

Missing Authentication for Critical Function (CWE-306)

2026-03-31 GitHub_M

Authentication Bypass Fastgpt

10.0

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

10.0 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 05:47 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

4.14.9.5

EUVD ID Assigned

Mar 31, 2026 - 14:30 euvd

EUVD-2026-17445

Analysis Generated

Mar 31, 2026 - 14:30 vuln.today

CVE Published

Mar 31, 2026 - 13:43 nvd

CRITICAL 10.0

DescriptionNVD

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.

AnalysisAI

Unauthenticated HTTP proxy abuse in FastGPT (AI Agent platform) prior to v4.14.9.5 allows remote attackers to relay arbitrary HTTP requests through the server. The /api/core/app/httpTools/runTool endpoint accepts user-controlled URLs, methods, headers, and body parameters without authentication, functioning as an open proxy for network pivoting, credential theft, and internal network reconnaissance. CVSS 10.0 (Critical) with network attack vector and no privileges required. No public exploit identified at time of analysis, though exploitation is trivial given the exposed endpoint design. EPSS data not available.

Technical ContextAI

FastGPT is an open-source AI Agent building platform (cpe:2.3:a:labring:fastgpt) that includes HTTP tool integration for agent workflows. The vulnerability stems from CWE-306 (Missing Authentication for Critical Function) in the HTTP tools testing endpoint. This endpoint was designed to test HTTP-based integrations but lacked authentication controls, allowing any network client to submit arbitrary HTTP requests that the FastGPT server executes on their behalf. The server-side request forgery (SSRF) capability is compounded by full control over destination URL, HTTP method (GET/POST/PUT/DELETE), custom headers (enabling authentication token injection), and request body content. The CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/S:C indicates network-accessible exploitation with no complexity barriers, no required privileges, no user interaction, and scope change - meaning attacks can pivot from the FastGPT server to reach otherwise inaccessible systems. The Changed scope reflects the proxy's ability to impact resources beyond the vulnerable component itself, including internal services, cloud metadata endpoints, and third-party APIs.

RemediationAI

Upgrade immediately to FastGPT version 4.14.9.5 or later, released by Labring to address this critical authentication bypass. The patch is available at https://github.com/labring/FastGPT/releases/tag/v4.14.9.5 with the security fix implemented in commit bc7eae2ed61481a5e322208829be291faec58c00 via pull request 6640 (https://github.com/labring/FastGPT/pull/6640). If immediate patching is not feasible, implement network-level controls to restrict access to the /api/core/app/httpTools/runTool endpoint, allowing only authenticated and authorized internal services. Deploy web application firewall (WAF) rules to block unauthenticated requests to paths matching /api/core/app/httpTools/* and monitor logs for suspicious outbound HTTP requests originating from the FastGPT server that may indicate exploitation attempts. Review server access logs for historical abuse of the endpoint, examining for requests to internal IP ranges (RFC 1918), cloud metadata endpoints (169.254.169.254), or unusual external domains. Conduct network segmentation review to limit blast radius if the FastGPT instance was previously exploited as a pivot point.