Vulnerability in openclaw (CVE-2026-45005)
Summary
Vulnerability in openclaw (CVE-2026-45005). Data can be tampered with by attackers. Exploitable via SecretRef. Mitigation: upgrade to 2026.4.23 or later.
Original description
The description as published by the source.
Summary
OpenClaw webhooks allowed route secrets to be backed by SecretRef values, but cached the resolved secret for a route. After an operator rotated the underlying secret and ran openclaw secrets reload, the previous resolved webhook secret could remain valid until the plugin or gateway restarted.
Impact
An attacker who already had a previously valid webhook route secret could continue authenticating webhook requests after the operator rotated the secret and reloaded secrets. This weakened credential rotation for webhook routes and could allow continued invocation of the configured webhook task flow until restart.
Affected Packages / Versions
- Package:
openclawon npm - Affected: versions before
2026.4.23 - Fixed:
2026.4.23 - Latest stable verified fixed:
openclaw@2026.4.23, tagv2026.4.23
Fix
Webhook route authentication now resolves SecretRef-backed route secrets on each request. A rotated secret becomes effective after openclaw secrets reload without requiring a gateway or plugin restart, and the old secret is rejected.
Fix Commit(s)
36c4a372a0ad5dca8bfc0d93f7aab9c2f2de66fa(fix(webhooks): reload route secrets per request)
Severity
Severity remains medium. The attack requires possession of a previously valid route secret, but the stale credential can continue to authorize webhook actions after rotation.
Source: GitHub Security Advisories (Global) 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-45005 has been found in openclaw.
Attackers can target a specific entry point like SecretRef over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.0/10.
What to do: upgrade openclaw to 2026.4.23 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-45005" on the vendor's site.
CVE-2026-45005 (openclaw) — CWE-613 / CVSS v3 6.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: SecretRef / openclaw / medium
Patched: 2026.4.23 — 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.
A vulnerability (CWE-613) exists in openclaw. Attackers reach the vulnerable code path via SecretRef.
Check the vendor advisory for the affected versions of openclaw. Attack surface: SecretRef / openclaw / medium.
Severity: Medium (CVSS 6.0/10). Data can be tampered with by attackers.
Update to 2026.4.23.
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.4.23ステージング環境で 2026.4.23 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web vulncheck.com
- web github.com
- web github.com