UTC
High

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

GHSA-gp3q-wpq4-5c5h · published 2026-03-12

Severity
High
CVSS score
7.1
Chance of exploitation (EPSS)
No CVE
Fixed in
2026.2.26
What it is

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

What to do

Upgrade openclaw to 2026.2.26 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

8bdda7a651c21e98faccdbbd73081e79cffe8be0 892a9c24b0f6118729ab5b5f5499b1a7e792dd15 (follow-up refactor hardening)

Affected
PackageRegistryAffectedFixed in
openclawnpm<= 2026.2.252026.2.26

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].