GHSA-gp3q-wpq4-5c5h
OpenClaw: LINE group allowlist scope mismatch with DM pairing-store entries
Summary
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)
Impact
This is a group-authorization scope mismatch. DM pairing-store entries could influence group sender authorization in allowlist mode.
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)
8bdda7a651c21e98faccdbbd73081e79cffe8be0892a9c24b0f6118729ab5b5f5499b1a7e792dd15(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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
What each source reports
GitHub Advisories Score used
OpenClaw: LINE group allowlist scope mismatch with DM pairing-store entries
Summary
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)
Impact
This is a group-authorization scope mismatch. DM pairing-store entries could influence group sender authorization in allowlist mode.
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)
8bdda7a651c21e98faccdbbd73081e79cffe8be0892a9c24b0f6118729ab5b5f5499b1a7e792dd15(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.
- Record
GHSA-gp3q-wpq4-5c5h- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N - Weakness
- CWE-863
- Updated
- 2026-11-02
OSV
OpenClaw: LINE group allowlist scope mismatch with DM pairing-store entries
Summary
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)
Impact
This is a group-authorization scope mismatch. DM pairing-store entries could influence group sender authorization in allowlist mode.
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)
8bdda7a651c21e98faccdbbd73081e79cffe8be0892a9c24b0f6118729ab5b5f5499b1a7e792dd15(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.
- Record
GHSA-gp3q-wpq4-5c5h- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N - Weakness
- CWE-863
- Updated
- 2026-11-02
Affected packages
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-gp3q-wpq4-5c5h is a high vulnerability (CVSS 7.1) in openclaw, published March 12, 2026. No source lists public exploit code. Fixed in openclaw 2026.2.26.