← Back
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.
AI summary snake-internal / snake-material-v2
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
@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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@utcp/http' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@utcp/http` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @utcp/http to 1.1.2ステージング環境で 1.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@utcp/http
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.1.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45366
- package https://github.com/universal-tool-calling-protocol/typescript-utcp
- web https://github.com/universal-tool-calling-protocol/typescript-utcp/security/advisories/GHSA-r8j5-8747-88cm
- web https://github.com/universal-tool-calling-protocol/python-utcp/issues/83
- web https://github.com/advisories/GHSA-r8j5-8747-88cm