Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45366 medium CVSS 4.7

SSRF (Server-Side Request Forgery) in @utcp/http (CVE-2026-45366)

Summary

SSRF in @utcp/http (CVE-2026-45366). Risk of unauthorized operations or information disclosure. Exploitable via toolCallTemplate.url. Mitigation: upgrade to 1.1.2 or later.

Original description

The description as published by the source.

Summary

The @utcp/http package is vulnerable to a blind Server-Side Request Forgery (SSRF) caused by a trust-boundary inconsistency between manual discovery and tool invocation. registerManual() validates the discovery URL against an HTTPS / loopback allowlist, but callTool() reuses the resolved toolCallTemplate.url directly without revalidating, and the OpenApiConverter blindly trusts whatever servers[0].url an attacker-hosted spec declares. An attacker who hosts a malicious OpenAPI spec on a legitimate HTTPS endpoint can declare e.g. servers: [{ url: "http://127.0.0.1:9090" }] or servers: [{ url: "http://169.254.169.254" }]; the converter then produces tools whose URL points at internal services on the agent host.

A separate prefix-bypass also affected the discovery-time check: the previous startsWith('http://localhost') guard let URLs like http://localhost.evil.com through.

Sister advisory

This is the npm/TypeScript counterpart of GHSA-39j6-4867-gg4w / CVE-2026-44661 on the Python utcp-http package. Same vulnerability, same fix shape, same reporter.

Versions and patch state

  • @utcp/http <= 1.1.1 — vulnerable. Both the loopback-redirect (http://127.0.0.1) and the non-loopback internal-IP variants (e.g. http://169.254.169.254, http://10.0.0.5) succeed. Note: the streamable_http and sse callToolStreaming paths in 1.1.1 ar…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45366 has been found in @utcp/http.
Attackers can target a specific entry point like toolCallTemplate.url over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: upgrade @utcp/http to 1.1.2 or later.
If unsure, ask your IT team or search "@utcp/http CVE-2026-45366" on the vendor's site.

CVE-2026-45366 (@utcp/http) — CWE-918 / CVSS v3 4.7
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: toolCallTemplate.url / OpenApiConverter / streamable_http / sse
Patched: 1.1.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in @utcp/http. Attackers reach the vulnerable code path via toolCallTemplate.url without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @utcp/http. Attack surface: toolCallTemplate.url / OpenApiConverter / streamable_http / sse.

🔥 Severity

Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.1.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@utcp/http' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@utcp/http' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @utcp/http を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @utcp/http to 1.1.2

    ステージング環境で 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @utcp/http
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.1.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details