Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Summary

The dangerouslyDisableSandbox parameter is exposed as part of the BashTool input schema, meaning the LLM (an untrusted principal per the project's own threat model) can set it to true in any tool_use response. Combined with the default allowUnsandboxedCommands: true setting, a prompt-injected model can escape the sandbox for any arbitrary command, achieving full host-level code execution.

Details

The vulnerability exists in the shouldUseSandbox() function in src/tools/BashTool/shouldUseSandbox.ts (lines 130–153):

export function shouldUseSandbox(input: Partial): boolean {
  if (!SandboxManager.isSandboxingEnabled()) {
    return false
  }
  // THE VULNERABILITY: model-controlled flag bypasses sandbox
  if (
    input.dangerouslyDisableSandbox &&
    SandboxManager.areUnsandboxedCommandsAllowed()
  ) {
    return false
  }
  // ...
  return true
}

The second guard, areUnsandboxedCommandsAllowed(), is defined in src/utils/sandbox/sandbox-adapter.ts (lines 474–477) and defaults to true:

function areUnsandboxedCommandsAllowed(): boolean {
  const settings = getSettings_DEPRECATED()
  return settings?.sandbox?.allowUnsandboxedCommands ?? true
}

This means that out of the box, with default configuration, the LLM can bypass the sandbox for any command simply by including "dangerouslyDisableSandbox": true in its tool call input. The project's own trust model states: "The model/agent is not a trusted…

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-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

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'openclaude' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で openclaude を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    set allowUnsandboxedCommands: false

    パッチが適用されるまでの応急処置として、set allowUnsandboxedCommands: false を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade openclaude to 0.5.1

    ステージング環境で 0.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm openclaude
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.5.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details