CVE-2026-26328

Under iMessage groupPolicy=allowlist, group authorization could be satisfied by sender identities coming from the DM pairing store, broadening DM trust into group contexts.

Details

Affected component: src/imessage/monitor/monitor-provider.ts.

Vulnerable logic derived effectiveGroupAllowFrom using both the static group allowlist and DM pairing-store identities (storeAllowFrom). This allowed a sender approved via DM pairing to satisfy group authorization in groups even if the sender/chat was not explicitly present in groupAllowFrom.

This weakens boundary separation between DM pairing and group allowlist authorization.

Affected Packages / Versions

• openclaw (npm): affected <= 2026.2.13
• clawdbot (npm): affected <= 2026.1.24-3

Fix Commit(s)

• openclaw/openclaw@872079d42fe105ece2900a1dd6ab321b92da2d59
• openclaw/openclaw@90d1e9cd71419168b2faa54a759b124a3eacfae7

Thanks @vincentkoc 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-26328 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. 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.2.14); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-26328? CVE-2026-26328 is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.2.14. It is fixed in 2026.2.14. 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-26328? CVE-2026-26328 has a CVSS score of 6.5 (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 packages are affected by CVE-2026-26328?
   • openclaw (npm) (versions < 2026.2.14)
   • clawdbot (npm) (versions < 2026.2.14)
4. Is there a fix for CVE-2026-26328? Yes. CVE-2026-26328 is fixed in 2026.2.14. Upgrade to this version or later.
5. Is CVE-2026-26328 exploitable, and should I be worried? Whether CVE-2026-26328 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-26328 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-26328?
   • Upgrade openclaw to 2026.2.14 or later
   • Upgrade clawdbot to 2026.2.14 or later