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

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

OpenClaw CVE-2026-41341

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

CVE-2026-41341 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-25325 LOW

Insufficient Type Distinction (CWE-351)

2026-04-23 VulnCheck

GHSA-pr66-whqj-rq5p

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 because exploitation requires a specific Group DM deployment context with the bot present; PR:L for authenticated Discord participant; 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:26 vuln.today

Analysis Generated

Jul 24, 2026 - 03:26 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-25325

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 a logic error in Discord component interaction routing that misclassifies group direct messages as direct messages in extensions/discord/src/monitor/agent-components-helpers.ts. Attackers can exploit this misclassification to bypass group DM policy enforcement or trigger incorrect session handling.

AnalysisAI

Incorrect channel type routing in OpenClaw's Discord extension (versions up to 2026.3.28) allows authenticated Group DM participants to bypass Group DM policy enforcement by exploiting a logic error that treats Group DMs as regular Direct Messages. The flaw in extensions/discord/src/monitor/agent-components-helpers.ts causes the isDirectMessage flag to be set based solely on the absence of a guild ID, which is also true for Group DM channels, causing all Group DM-specific authorization checks (the groupEnabled toggle and channel allowlist) to be silently skipped. No public exploit exists, this vulnerability is not in the CISA KEV catalog, and EPSS at 0.01% (2nd percentile) reflects negligible exploitation interest.

Technical ContextAI

OpenClaw is an npm-distributed AI agent framework that integrates with Discord bots, exposing interactive components (buttons, dropdowns) through Discord's component interaction API. The root cause is CWE-351 (Insufficient Type Distinction): the original resolveComponentInteractionContext function computed isDirectMessage = !rawGuildId, which evaluates to true for both ChannelType.DM and ChannelType.GroupDM channels because neither carries a guild ID in Discord's API. Group DMs were consequently routed through the direct-message code path, bypassing the dedicated ensureGroupDmComponentAuthorized authorization logic that checks discordConfig.dm.groupEnabled and validates against the configured channel allowlist. The patch (commit 8c83128fc38d5a3642b8ccbea58550755fdbbbaf) explicitly detects ChannelType.GroupDM via Discord's channel type API, introduces a separate isGroupDm routing flag, and adds the ensureGroupDmComponentAuthorized function that enforces Group DM policy before allowing interaction dispatch. Affected CPE: cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*, versions <= 2026.3.28.

RemediationAI

Upgrade the openclaw npm package to version 2026.3.31 or later, which contains the fix from commit 8c83128fc38d5a3642b8ccbea58550755fdbbbaf (merged 2026-03-30) as confirmed by the vendor GHSA advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-6336-qqw9-v6x6. If immediate upgrade is not possible, set the discordConfig.dm.groupEnabled configuration option to false (which is already the default), which causes even the pre-patch code to block Group DM interactions via the DM code path's own checks; this eliminates Group DM access entirely as a trade-off for mitigating the bypass. Environments that do not expose the bot in Group DM contexts are not exposed to this vulnerability and require no immediate action beyond planning an upgrade.