Categories
CVE-2026-43577

Vulnerability in openclaw (CVE-2026-43577)

Summary

Vulnerability in openclaw (CVE-2026-43577). Risk of unauthorized operations or information disclosure. Exploitable via openclaw. Mitigation: upgrade to 2026.4.9 or later.

Original description

The description as published by the source.

Summary

Browser interaction routes could pivot into local CDP and regain file reads.

Affected Packages / Versions

  • Package: openclaw
  • Ecosystem: npm
  • Affected versions: < 2026.4.9
  • Patched versions: >= 2026.4.9

Impact

Browser act/evaluate interactions could trigger navigation into the local CDP origin and then create or read disallowed file:// pages despite direct navigation guards.

Technical Details

The fix re-checks browser URLs after interaction-driven navigations and blocks targets that violate the configured navigation policy.

Fix

The issue was fixed in #63226. The first stable tag containing the fix is v2026.4.9, and openclaw@2026.4.14 includes the fix.

Fix Commit(s)

  • 5f5b3d733bdd791cb457f838514179e1288b10b3
  • PR: #63226

Release Process Note

Users should upgrade to openclaw 2026.4.9 or newer. The latest npm release, 2026.4.14, already includes the fix.

Credits

Thanks to @tdjackey for reporting this issue.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-43577 has been found in openclaw.
Attackers can target a specific entry point like openclaw over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to 2026.4.9 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-43577" on the vendor's site.

CVE-2026-43577 (openclaw) — CWE-693
Attack surface: openclaw
Patched: 2026.4.9 — 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

A vulnerability (CWE-693) exists in openclaw. Attackers reach the vulnerable code path via openclaw.

📍 Affected scope

Check the vendor advisory for the affected versions of openclaw. Attack surface: openclaw.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2026.4.9.

🛡️ 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.4.9

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

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

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

Affected packages

npm openclaw
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.4.9"}]}]

References

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