NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

OpenClaw: LINE group allowlist scope mismatch with DM pairing-store entriesGHSA-gp3q-wpq4-5c5h

HIGHFix: openclaw/openclaw@892a9c2

GHSA-gp3q-wpq4-5c5h is a high-severity (CVSS 7.1) vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Mar 14, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
openclawnpm
2.5Mdownloads / week

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmopenclawall versions2026.2.26npm install openclaw@2026.2.26

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update openclaw to 2026.2.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gp3q-wpq4-5c5h is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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: gr
O3 Security · Impact-Aware SCA

Is GHSA-gp3q-wpq4-5c5h in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
OpenClaw: LINE group allowlist scope mismatch with DM…