Skip to content
Fencer Intel
high 7.1

GHSA-gp3q-wpq4-5c5h json

OpenClaw: LINE group allowlist scope mismatch with DM pairing-store entries

published 8mo ago modified 7mo ago

cvss
7.1
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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) - `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.

Patch / fix

  • npm openclaw 2026.2.26

Is GHSA-gp3q-wpq4-5c5h in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm openclaw
<2026.2.26
2026.2.26

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of openclaw/openclaw published their own advisory on GitHub. Reviewed sources take precedence over it.