Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-53840 high CVSS 7.1

Information Disclosure in openclaw (CVE-2026-53840)

Summary

Vulnerability in openclaw (CVE-2026-53840). Confidential information can be exposed externally. Mitigation: upgrade to 2026.5.12 or later.

Original description

The description as published by the source.

Summary

OpenClaw supports remote MCP Streamable HTTP servers with operator-configured custom headers. In affected releases, those headers could be forwarded when the MCP endpoint responded with a cross-origin redirect.

This issue is limited to configured MCP Streamable HTTP servers that use custom headers. It does not expose unrelated OpenClaw credentials.

Affected configurations

This affects deployments where an MCP server is configured with:

  • transportType: "streamable-http"
  • sensitive custom headers under mcp.servers.*.headers
  • an MCP endpoint that is malicious, compromised, or able to redirect to another origin

Impact

Custom MCP headers, such as API keys or tenant-routing headers, could be sent to the redirect target. The exposed credential scope depends on the header the operator configured for that MCP server.

Patched Versions

The first stable patched version is 2026.5.12.

Mitigations

Upgrade to openclaw@2026.5.8 or later. Before upgrading, avoid custom MCP headers with servers you do not fully trust, and rotate any MCP-specific credentials that may have been exposed by a redirecting endpoint.

Source: NIST National Vulnerability Database 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-53840 has been found in openclaw.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade openclaw to 2026.5.12 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-53840" on the vendor's site.

CVE-2026-53840 (openclaw) — CWE-200 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 2026.5.12 — 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.

❓ What is the problem

Information disclosure (CWE-200) exists in openclaw.

📍 Affected scope

Check the vendor advisory for the affected versions of openclaw.

🔥 Severity

Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2026.5.12.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 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

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

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

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

  2. 2
    Apply patch patch 
    Upgrade openclaw to 2026.5.12

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

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

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

Affected packages

pip openclaw
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
npm openclaw
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.5.12"}]}]

References

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