Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44992 medium CVSS 5.0

Vulnerability in openclaw (CVE-2026-44992)

Summary

Vulnerability in openclaw (CVE-2026-44992). Confidential information can be exposed externally. Exploitable via openclaw. Mitigation: upgrade to 2026.4.20 or later.

Original description

The description as published by the source.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Affected versions: >= 2026.4.5, < 2026.4.20
  • Patched version: 2026.4.20

Impact

A malicious workspace .env could set MINIMAX_API_HOST and redirect credentialed MiniMax requests to an attacker-controlled origin, exposing the MiniMax API key in the outbound Authorization header.

This requires running OpenClaw from an attacker-controlled workspace. Severity is medium.

Fix

OpenClaw now blocks MINIMAX_API_HOST from workspace dotenv injection and removes env-driven URL routing from the affected MiniMax request path.

Fix commit:

  • 2f06696579a1ab0cb5bbbbb6a900414a6b2e3cd1

Release

Fixed in OpenClaw 2026.4.20.

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-44992 has been found in openclaw.
Attackers can target a specific entry point like openclaw over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.0/10.
What to do: upgrade openclaw to 2026.4.20 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-44992" on the vendor's site.

CVE-2026-44992 (openclaw) — CWE-15 / CVSS v3 5.0
Attack vector: local
Attack surface: openclaw / MINIMAX_API_HOST / Authorization
Patched: 2026.4.20 — 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-15) 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 / MINIMAX_API_HOST / Authorization.

🔥 Severity

Severity: Medium (CVSS 5.0/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2026.4.20.

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

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

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

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

Affected packages

npm openclaw
[{"type":"SEMVER","events":[{"introduced":"2026.4.5"},{"fixed":"2026.4.20"}]}]

References

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