Is there a patch available for CVE-2026-41348?

Yes, a patch is available for CVE-2026-41348. Update the affected software to the latest version immediately.

OpenClaw CVE-2026-41348

Q: What is the CVSS score of CVE-2026-41348?

CVE-2026-41348 has a CVSS 4.0 base score of 2.3 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-25332 LOW

Incorrect Authorization (CWE-863)

2026-04-23 VulnCheck

GHSA-qgp3-3rj7-qqq4

Authentication Bypass Openclaw

2.3

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

2.3 LOW

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

4.2 MEDIUM

AC:H reflects AT:P requirement (allowlist must be configured); PR:L for existing Discord authorization; no availability impact.

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

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 03:23 vuln.today

Analysis Generated

Jul 24, 2026 - 03:23 vuln.today

Severity Changed

Apr 23, 2026 - 22:28 NVD

MEDIUM LOW

CVSS changed

Apr 23, 2026 - 22:28 NVD

5.4 (MEDIUM) 2.3 (LOW)

EUVD ID Assigned

Apr 23, 2026 - 22:15 euvd

EUVD-2026-25332

Patch released

Apr 23, 2026 - 22:15 nvd

Patch available

CVE Published

Apr 23, 2026 - 21:58 nvd

LOW 2.3

Blast Radius

ecosystem impact

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

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

Ecosystem-wide dependent count for version 2026.3.31.

DescriptionCVE.org

OpenClaw before 2026.3.31 contains an authorization bypass vulnerability in Discord slash command and autocomplete paths that fail to enforce group DM channel allowlist restrictions. Authorized Discord users can bypass channel restrictions by invoking slash commands, allowing access to restricted group DM channels.

AnalysisAI

OpenClaw's Discord integration (npm package, versions <= 2026.3.28) exposes an authorization bypass where authenticated Discord users invoke slash commands or trigger autocomplete in group DM channels outside the configured allowlist, circumventing the dm.groupChannels restriction in both the command dispatch and autocomplete paths. The impact is bounded: exploitation requires an already-authorized Discord user and a deployment with group DM allowlisting actively configured, limiting the trust boundary crossed to channel-level access rather than a broader privilege escalation. EPSS is 0.03% (7th percentile) and SSVC classifies exploitation as none; no public exploit code exists and the issue is not in CISA KEV.

Technical ContextAI

OpenClaw is an npm package (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) providing a Discord bot integration layer. The vulnerable code resides in extensions/discord/src/monitor/native-command.ts, where the handlers for Discord native slash commands and autocomplete interactions failed to invoke the resolveGroupDmAllow() gate before dispatching to the plugin system. The root cause is CWE-863 (Incorrect Authorization): the allowlist check was present for some paths but absent in the slash command and autocomplete routing branches, allowing the dm.groupChannels configuration to be silently bypassed. The fix introduced a unified resolveDiscordNativeGroupDmAccess() function that is called consistently across both the run and autocomplete paths, returning explicit allow/deny decisions with typed reasons ('disabled' or 'not-allowlisted').

RemediationAI

Upgrade the OpenClaw npm package to version 2026.3.31 or later, which is the first stable release containing the fix per the GHSA advisory (https://github.com/openclaw/openclaw/security/advisories/GHSA-rvvf-6vh3-9j43). The specific patch is available at commit 8fdb19676ab44cf85d47ee13c578195f2e527591 (https://github.com/openclaw/openclaw/commit/8fdb19676ab44cf85d47ee13c578195f2e527591). If immediate upgrade is not possible and a dm.groupChannels allowlist is in use, a compensating control is to disable group DM functionality entirely by setting dm.groupEnabled: false in the Discord channel configuration - this eliminates the vulnerable code path at the cost of disabling all group DM interactions. Deployments that do not use the dm.groupChannels allowlist feature are not exposed to meaningful risk from this bypass.