Q: How to self-check? (Features/Scanning)

🔎 **Check**: Verify if your OpenClaw version is **< 2026.3.12**. <br>👀 **Scan**: Look for Zalouser allowlist configurations relying on **display names** instead of unique IDs.

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

✅ **Fixed**: Yes. <br>🔧 **Patch**: Upgrade to **OpenClaw 2026.3.12** or later. <br>📝 **Ref**: GitHub Advisory GHSA-f5mf-3r52-r83w.

Q: What if no patch? (Workaround)

🚧 **Workaround**: If unpatched, **disable Zalouser allowlist** or enforce **immutable group IDs** in configuration. Restrict group creation permissions.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. <br>🚀 **Priority**: **Immediate Action**. CVSS Score is **High** (likely 9.8). Remote, unauthenticated, full impact. Patch NOW.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: OpenClaw's Zalouser allowlist uses **mutable group display names** instead of stable IDs.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **CWE**: CWE-807 (Security Misinterpretation).
🔍 **Flaw**: The system matches against **variable display names** rather than immutable identifiers, leading to weak authorization logic.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Vendor**: OpenClaw.
📉 **Affected**: Versions **before 2026.3.12**.
⚙️ **Component**: Zalouser allowlist module.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Privileges**: Full bypass of channel/group authorization.
📂 **Data**: Potential access to private chats, files, and restricted content within the impersonated group context.

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

📊 **Threshold**: **LOW**.
🔑 **Auth**: No authentication required (PR:N).
🌐 **Network**: Remote (AV:N).
👤 **UI**: None required (UI:N).

Question 6

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

Accepted Answer

🧨 **Exploit**: **No public PoC** listed in data.
🌍 **Wild Exploit**: Unconfirmed, but logic is simple (name spoofing), making theoretical exploitation high.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔎 **Check**: Verify if your OpenClaw version is **< 2026.3.12**.
👀 **Scan**: Look for Zalouser allowlist configurations relying on **display names** instead of unique IDs.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fixed**: Yes.
🔧 **Patch**: Upgrade to **OpenClaw 2026.3.12** or later.
📝 **Ref**: GitHub Advisory GHSA-f5mf-3r52-r83w.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **Workaround**: If unpatched, **disable Zalouser allowlist** or enforce **immutable group IDs** in configuration. Restrict group creation permissions.

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **CRITICAL**.
🚀 **Priority**: **Immediate Action**. CVSS Score is **High** (likely 9.8). Remote, unauthenticated, full impact. Patch NOW.

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

CVE-2026-32975 — 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