← Back
CVE-2026-42074
critical
CVSS 9.8
Vulnerability in openclaude (CVE-2026-42074)
Summary
vulnerability in openclaude (CVE-2026-42074). Successful exploitation can lead to full system takeover. Exploitable via ``dangerouslyDisableSandbox``. Mitigation: upgrade to `0.5.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42074** has been found in openclaude.
Attackers can target a specific entry point like ``dangerouslyDisableSandbox`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade openclaude to **0.5.1** or later.
If unsure, ask your IT team or search "openclaude CVE-2026-42074" on the vendor's site.
CVE-2026-42074 (openclaude) — CWE-284 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `dangerouslyDisableSandbox` / `true` / `tool_use` / `input.dangerouslyDisableSandbox`
Patched: `0.5.1` — apply immediately
Workaround: set allowUnsandboxedCommands: false
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-284) exists in openclaude. Attackers reach the vulnerable code path via ``dangerouslyDisableSandbox`` without authentication.
📍 Affected scope
openclaude — . Attack surface: `dangerouslyDisableSandbox` / `true` / `tool_use` / `input.dangerouslyDisableSandbox`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **0.5.1**.
🛡️ Workaround
Workaround: set allowUnsandboxedCommands: false
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'openclaude' .` 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 'openclaude' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `openclaude` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
set allowUnsandboxedCommands: falseパッチが適用されるまでの応急処置として、set allowUnsandboxedCommands: false を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade openclaude to 0.5.1ステージング環境で 0.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
openclaude
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.5.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-42074
- package https://github.com/Gitlawb/openclaude
- web https://github.com/Gitlawb/openclaude/security/advisories/GHSA-m77w-p5jj-xmhg
- web https://github.com/Gitlawb/openclaude/pull/778
- web https://github.com/Gitlawb/openclaude/commit/aab489055c53dd64369414116fe93226d2656273
- web https://github.com/advisories/GHSA-m77w-p5jj-xmhg