Server-Side Request Forgery (SSRF) Affecting tempo2.10 package, versions <0:2.10.8-0.2.hum1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.22% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-TEMPO210-19523305
  • published4 Sept 2026
  • disclosed27 Aug 2026

Introduced: 27 Aug 2026

CVE-2026-81092  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade RHEL:10 tempo2.10 to version 0:2.10.8-0.2.hum1 or higher.
This issue was patched in RHSA-2026:62527.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tempo2.10 package and not the tempo2.10 package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

mcp-go accepted requests on its HTTP transports without checking the Host header. StreamableHTTPServer.ServeHTTP in server/streamable_http.go and SSEServer.ServeHTTP in server/sse.go served any request arriving over a loopback connection regardless of the host it named, and the SSE transport's cross-origin default allowed any origin. A page in a browser could therefore point a name it controlled at the loopback address and reach a server listening there, invoking tools and reading resources that the server exposed on the assumption that only local software could connect. No release before 0.56.0 validated the header on either transport; 0.56.0 adds server/http_localhost.go, which rejects a loopback-bound request carrying a host that is not a loopback name, and wires it into both transports.

CVSS Base Scores

version 3.1