SSRF (Server-Side Request Forgery) in openclaw (CVE-2026-41361)
Summary
SSRF in openclaw (CVE-2026-41361). Risk of unauthorized operations or information disclosure. Exploitable via d61f8e5672. Mitigation: upgrade to >= 2026.3.28 or later.
Original description
The description as published by the source.
Summary
The SSRF/IP classifier treated several IPv6 special-use ranges as public and allowed fetches to proceed.
Impact
An attacker who controlled a fetched URL could target internal or non-routable IPv6 addresses that should have been blocked by the SSRF guard.
Affected Component
src/shared/net/ip.ts, src/infra/net/ssrf.*
Fixed Versions
- Affected:
<= 2026.3.24 - Patched:
>= 2026.3.28 - Latest stable
2026.3.28contains the fix.
Fix
Fixed by commit d61f8e5672 (Net: block missing IPv6 special-use ranges).
OpenClaw thanks @nicky-cc of Tencent zhuque Lab https://github.com/Tencent/AI-Infra-Guard for reporting.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-41361 has been found in openclaw.
Attackers can target a specific entry point like d61f8e5672 over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to >= 2026.3.28 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-41361" on the vendor's site.
CVE-2026-41361 (openclaw) — CWE-918
Attack vector: remote (network-reachable) / no user interaction
Attack surface: d61f8e5672
Patched: >= 2026.3.28 — 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.
SSRF (CWE-918) exists in openclaw. Attackers reach the vulnerable code path via d61f8e5672.
Check the vendor advisory for the affected versions of openclaw. Attack surface: d61f8e5672.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to >= 2026.3.28.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openclaw' . 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 'openclaw' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openclawを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade openclaw to >= 2026.3.28ステージング環境で >= 2026.3.28 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com