SSRF (Server-Side Request Forgery) in UTMStack (CVE-2026-82040)
Summary
SSRF in UTMStack (CVE-2026-82040). Risk of unauthorized operations or information disclosure. Exploitable via PUT /api/identity-providers.
Original description
The description as published by the source.
UTMStack before 11.2.16 contains a server-side request forgery vulnerability in IdentityProviderService.validateMetadataUrl() that allows authenticated attackers to make the server send requests to arbitrary internal or cloud metadata hosts by supplying a malicious metadata URL to the identity-providers endpoint. Attackers can exploit the POST/PUT /api/identity-providers endpoint with no validation of target host, IP, or scheme to perform internal network port scanning and access cloud instance-metadata services.
Source: NIST National Vulnerability Database 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-82040 has been found in UTMStack.
Attackers can target a specific entry point like PUT /api/identity-providers over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "UTMStack CVE-2026-82040" on the vendor's site.
CVE-2026-82040 (UTMStack) — CWE-918 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /api/identity-providers
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.
SSRF (CWE-918) exists in UTMStack. Attackers reach the vulnerable code path via PUT /api/identity-providers.
Check the vendor advisory for the affected versions of UTMStack. Attack surface: PUT /api/identity-providers.
Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /api/identity-providers requests with malformed payloads or SQL meta-characters. Run grep -r 'UTMStack' . 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
-
1Identify exposure identify
grep -r 'UTMStack' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
UTMStackを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PUT /api/identity-providers' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /api/identity-providersへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /api/identity-providers on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com