Authorization Flaw in openclaw (CVE-2026-41353)
Summary
Vulnerability in openclaw (CVE-2026-41353). Risk of unauthorized operations or information disclosure. Exploitable via allowProfiles. Mitigation: upgrade to 2026.3.22 or later.
Original description
The description as published by the source.
Summary
Node browser proxy allowProfiles bypass through persistent profile mutation and runtime profile selection
Current Maintainer Triage
- Status: open
- Normalized severity: high
- Assessment: Real released allowProfiles bypass through profile mutation and runtime profile selection, fixed and shipped in v2026.3.22+, so keep open for publish rather than close.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version:
2026.3.31 - Vulnerable version range:
<=2026.3.13-1 - Patched versions:
>= 2026.3.22 - First stable tag containing the fix:
v2026.3.22
Fix Commit(s)
eac93507c36ccd0c359fba18fa466ef6448be8a5— 2026-03-23T00:56:44-07:00
Release Process Note
- The fix is already present in released version
2026.3.22. - This draft looks ready for final maintainer disposition or publication, not additional code-fix work.
Thanks @smaeljaish771 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-41353 has been found in openclaw.
Attackers can target a specific entry point like allowProfiles over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to 2026.3.22 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-41353" on the vendor's site.
CVE-2026-41353 (openclaw) — CWE-863
Attack surface: allowProfiles / openclaw / eac93507c36ccd0c359fba18fa466ef6448be8a5
Patched: 2026.3.22 — 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.
Incorrect authorization (CWE-863) exists in openclaw. Attackers reach the vulnerable code path via allowProfiles.
Check the vendor advisory for the affected versions of openclaw. Attack surface: allowProfiles / openclaw / eac93507c36ccd0c359fba18fa466ef6448be8a5.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.3.22.
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.22ステージング環境で 2026.3.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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