Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44113 high CVSS 7.7

Vulnerability in openclaw (CVE-2026-44113)

Summary

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

Original description

The description as published by the source.

Summary

OpenShell FS bridge reads pin and verify the opened file before returning bytes

Affected Packages / Versions

  • Package: openclaw (npm)
  • Affected versions: <= 2026.4.21
  • Fixed version: 2026.4.22

Impact

A time-of-check/time-of-use race around OpenShell sandbox filesystem reads could let a symlink swap cause bytes outside the intended mount root to be read.

Fix

OpenShell reads now open the file with no-follow semantics where available, validate the pinned file descriptor against the canonical mount root, reject unsafe hardlink/symlink cases, and use a strict fallback ancestor walk on platforms without fd-path readback.

Fix Commit(s)

  • 95119017c847c737bd113f0bff728c4666d79c45

Verification

  • The fix commit is contained in the public v2026.4.22 tag.
  • openclaw@2026.4.22 is published on npm and the compiled package contains the fix.
  • Focused regression coverage for this path passed before publication.

Thanks @VladimirEliTokarev for reporting.

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

CVE-2026-44113 (openclaw) — CWE-367 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 2026.4.22 — 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-367) exists in openclaw.

📍 Affected scope

Check the vendor advisory for the affected versions of openclaw.

🔥 Severity

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

🔧 How to fix

Update to 2026.4.22.

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

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

  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.22"}]}]

References

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