CVE-2026-41406

Feishu thread history and quoted messages bypass sender allowlist

Current Maintainer Triage

• Status: open
• Normalized severity: medium
• Assessment: Real in shipped v2026.3.28 Feishu because fetched quoted/root/thread context bypasses sender allowlists, and SECURITY.md does not exempt remote sender-allowlist bypasses.

Affected Packages / Versions

• Package: openclaw (npm)
• Latest published npm version: 2026.3.31
• Vulnerable version range: <=2026.3.28
• Patched versions: >= 2026.3.31
• First stable tag containing the fix: v2026.3.31

Fix Commit(s)

• f45e5a6569aab1d58cc6de25b19f1dc4c8779b85, 2026-03-31T19:43:54+09:00

Release Process Note

• The fix is already present in released version 2026.3.31.
• This draft looks ready for final maintainer disposition or publication, not additional code-fix work.

OpenClaw thanks @AntAISecurityLab for reporting.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-41406 has a CVSS score of 5.4 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.3.31); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-41406? CVE-2026-41406 is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.3.28. It is fixed in 2026.3.31. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-41406? CVE-2026-41406 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-41406? openclaw (npm) versions <= 2026.3.28 is affected.
4. Is there a fix for CVE-2026-41406? Yes. CVE-2026-41406 is fixed in 2026.3.31. Upgrade to this version or later.
5. Is CVE-2026-41406 exploitable, and should I be worried? Whether CVE-2026-41406 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-41406 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-41406? Upgrade openclaw to 2026.3.31 or later.