GHSA-GP3Q-WPQ4-5C5H

In specific LINE configurations, sender IDs approved through DM pairing could also satisfy group allowlist checks when operators expected group sender access to be scoped only to explicit group allowlists.

Affected Packages / Versions

• Package: openclaw (npm)
• Latest published version at triage/update time: 2026.2.25
• Affected: <= 2026.2.25
• Patched: >= 2026.2.26 (planned next release)

Technical Details

Root cause: group allowlist composition inherited pairing-store entries intended for DM approvals. Under default DM pairing policy, a DM-paired sender could match group allowlist checks.

Fixes on main:

• isolate group allowlist composition from pairing-store entries
• centralize shared DM/group allowlist composition to preserve DM-only pairing behavior
• add regression coverage for LINE and Mattermost policy paths

Fix Commit(s)

• 8bdda7a651c21e98faccdbbd73081e79cffe8be0
• 892a9c24b0f6118729ab5b5f5499b1a7e792dd15 (follow-up refactor hardening)

Release Process Note

patched_versions is pre-set to >= 2026.2.26 so once npm 2026.2.26 is published, this advisory can be published directly without additional version-field edits.

Thanks @tdjackey for reporting.

This is a group-authorization scope mismatch. DM pairing-store entries could influence group sender authorization in allowlist mode.

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.

GHSA-GP3Q-WPQ4-5C5H has a CVSS score of 7.1 (High). 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.26); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-GP3Q-WPQ4-5C5H? GHSA-GP3Q-WPQ4-5C5H is a high-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.2.25. It is fixed in 2026.2.26. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is GHSA-GP3Q-WPQ4-5C5H? GHSA-GP3Q-WPQ4-5C5H has a CVSS score of 7.1 (High). 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 GHSA-GP3Q-WPQ4-5C5H? openclaw (npm) versions <= 2026.2.25 is affected.
4. Is there a fix for GHSA-GP3Q-WPQ4-5C5H? Yes. GHSA-GP3Q-WPQ4-5C5H is fixed in 2026.2.26. Upgrade to this version or later.
5. Is GHSA-GP3Q-WPQ4-5C5H exploitable, and should I be worried? Whether GHSA-GP3Q-WPQ4-5C5H 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 GHSA-GP3Q-WPQ4-5C5H 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 GHSA-GP3Q-WPQ4-5C5H? Upgrade openclaw to 2026.2.26 or later.