What is the CVSS score of EUVD-2026-13021?

EUVD-2026-13021 has a CVSS 3.1 base score of 3.7 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of Openclaw are affected by EUVD-2026-13021?

CVE-2026-31991 is a low-severity vulnerability (CVSS 3.7). The limited severity suggests constrained impact, typically requiring specific conditions or local access for exploitation.. A patch is available.

How to fix or mitigate EUVD-2026-13021?

During next maintenance window: Apply vendor patches when convenient. Vendor patch is available.

Openclaw EUVD-2026-13021

| CVE-2026-31991 LOW

Incorrect Authorization (CWE-863)

2026-03-19 VulnCheck

GHSA-wm8r-w8pf-2v6w

Authentication Bypass Openclaw

3.7

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

3.7 LOW

AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 19, 2026 - 01:30 euvd

EUVD-2026-13021

Analysis Generated

Mar 19, 2026 - 01:30 vuln.today

Patch released

Mar 19, 2026 - 01:30 nvd

Patch available

CVE Published

Mar 19, 2026 - 01:00 nvd

LOW 3.7

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

2 npm packages depend on openclaw (2 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.2.26.

DescriptionCVE.org

OpenClaw versions prior to 2026.2.26 contain an authorization bypass vulnerability where Signal group allowlist policy incorrectly accepts sender identities from DM pairing-store approvals. Attackers can exploit this boundary weakness by obtaining DM pairing approval to bypass group allowlist checks and gain unauthorized group access.

AnalysisAI

OpenClaw versions prior to 2026.2.26 contain an authorization bypass vulnerability in Signal group allowlist enforcement where the system incorrectly accepts sender identities derived from direct message (DM) pairing-store approvals. An authenticated attacker with low privileges can exploit this boundary weakness by obtaining DM pairing approval, allowing them to bypass group allowlist checks and gain unauthorized access to Signal groups. While the CVSS score is moderate (3.7) and attack complexity is high, the vulnerability represents a direct authentication control bypass in a messaging security context, and patches are available from the vendor.

Technical ContextAI

The vulnerability exists in OpenClaw's Signal group access control implementation, which relies on an allowlist policy to restrict group membership. The root cause is classified under CWE-863 (Incorrect Authorization), specifically a logic flaw where the authorization module fails to properly validate the source of sender identity claims. When a user obtains DM pairing-store approval (a mechanism typically used for direct messaging authentication), the vulnerable code incorrectly accepts these DM-sourced identities as valid credentials for Signal group access decisions. The affected products are identified via CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:* for all versions prior to 2026.2.26. The flaw represents a boundary confusion issue between two distinct trust domains (DM pairing context and group allowlist context), allowing privilege escalation from authenticated DM user to unauthorized group member.

RemediationAI

Upgrade OpenClaw to version 2026.2.26 or later immediately, as patches are available from the vendor via commits 8bdda7a651c21e98faccdbbd73081e79cffe8be0 and 64de4b6d6ae81e269ceb4ca16f53cda99ced967a (see https://github.com/openclaw/openclaw/security/advisories/GHSA-wm8r-w8pf-2v6w for full advisory). If immediate patching is not possible, implement network segmentation to restrict DM pairing approval flows only to trusted, internal systems and audit Signal group membership assignments to detect unauthorized access attempts. Additionally, review and strengthen DM pairing approval workflows to ensure they cannot be misused to influence group allowlist decisions, and consider implementing additional authorization checks that validate the context (DM vs. group) of each identity claim before granting group access.