← Back
CVE-2026-44991
medium
CVSS 4.2
Vulnerability in openclaw (CVE-2026-44991)
Summary
vulnerability in openclaw (CVE-2026-44991). Risk of unauthorized operations or information disclosure. Exploitable via ``commands.ownerAllowFrom``. Mitigation: upgrade to `2026.4.21` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44991** has been found in openclaw.
Attackers can target a specific entry point like ``commands.ownerAllowFrom`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: upgrade openclaw to **2026.4.21** or later.
If unsure, ask your IT team or search "openclaw CVE-2026-44991" on the vendor's site.
CVE-2026-44991 (openclaw) — CWE-862 / CVSS v3 4.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `commands.ownerAllowFrom` / `openclaw` / `allowFrom` / `main`
Patched: `2026.4.21` — apply immediately
Workaround: Upgrade to `[email protected]` or later.
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
**A vulnerability** (CWE-862) exists in openclaw. Attackers reach the vulnerable code path via ``commands.ownerAllowFrom`` without authentication.
📍 Affected scope
openclaw — . Attack surface: `commands.ownerAllowFrom` / `openclaw` / `allowFrom` / `main`.
🔥 Severity
Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2026.4.21**.
🛡️ Workaround
Workaround: Upgrade to `[email protected]` or later.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Upgrade to `[email protected]` or later.パッチが適用されるまでの応急処置として、Upgrade to `[email protected]` or later. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade openclaw to 2026.4.21ステージング環境で 2026.4.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
openclaw
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2026.4.21"}]}]
References
- package https://github.com/openclaw/openclaw
- web https://github.com/openclaw/openclaw/security/advisories/GHSA-c28g-vh7m-fm7v
- web https://nvd.nist.gov/vuln/detail/CVE-2026-44991
- web https://github.com/openclaw/openclaw/commit/2aa93d44a1b2c7058c371f261fda2b5d4de4a882
- web https://github.com/openclaw/openclaw/commit/995febb7b1e811ff6a1df5b18c22de94103f4c9f
- web https://www.vulncheck.com/advisories/openclaw-authorization-bypass-in-owner-enforced-commands-via-wildcard-channel-senders
- web https://github.com/advisories/GHSA-p3pv-c954-9m6f
- web https://github.com/advisories/GHSA-c28g-vh7m-fm7v