Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed?**: **Yes**. 🩹 **Patch**: Update to **OpenClaw 2026.2.23** or later. 📢 **Source**: See GitHub Advisory GHSA-3c6h-g97w-fg78 for official details.

Q: What if no patch? (Workaround)

🚧 **No Patch?**: Implement strict **Input Validation**. 🛑 **Workaround**: Restrict `safeBins` to a known-good whitelist. Disable `tools.exec` if not needed. Apply network segmentation.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **Critical**. 🚨 **Priority**: Patch immediately. ⏳ **Reason**: CVSS is High. Network-accessible. Low exploitation barrier. Do not wait for PoC.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: OpenClaw (pre-2026.2.23) has a critical flaw in `tools.exec.safeBins`.
💥 **Consequences**: Attackers can bypass safety checks. This leads to **unauthorized code execution**.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-184** (Incomplete List of Disallowed Inputs).
🔍 **Flaw**: The validation logic for `safeBins` is insufficient. It fails to block malicious inputs effectively, allowing bypass.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: **OpenClaw** by vendor OpenClaw.
📅 **Versions**: All versions **before 2026.2.23**.
⚠️ **Component**: The `tools.exec` module specifically.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

👑 **Privileges**: High Impact. CVSS Score indicates **High** Confidentiality, Integrity, and Availability impact.
📂 **Data**: Attackers can execute arbitrary code.…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

🔐 **Threshold**: **Low**.
📝 **Config**: CVSS `PR:L` (Low Privileges) required. `AV:N` (Network) and `UI:N` (No User Interaction).
🚀 **Ease**: `AC:L` (Low Complexity). Easy to exploit if network access exists.

Question 6

Is there a public Exp? (PoC/Wild Exploitation)

Accepted Answer

🕵️ **Public Exp?**: **No**.
📄 **PoC**: The `pocs` field is empty.
🌍 **Wild Exp**: No reports of wild exploitation yet. However, the low complexity makes it a prime target.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**: Check your OpenClaw version.
📉 **Scan**: Look for versions **< 2026.2.23**.
🛠️ **Feature**: Inspect `tools.exec.safeBins` configuration. Ensure strict input validation is in place.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fixed?**: **Yes**.
🩹 **Patch**: Update to **OpenClaw 2026.2.23** or later.
📢 **Source**: See GitHub Advisory GHSA-3c6h-g97w-fg78 for official details.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch?**: Implement strict **Input Validation**.
🛑 **Workaround**: Restrict `safeBins` to a known-good whitelist. Disable `tools.exec` if not needed. Apply network segmentation.

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **Critical**.
🚨 **Priority**: Patch immediately.
⏳ **Reason**: CVSS is High. Network-accessible. Low exploitation barrier. Do not wait for PoC.

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2026-28363 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

Q6Is there a public Exp? (PoC/Wild Exploitation)

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring