Is there a patch available for EUVD-2026-26116?

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

OpenClaw EUVD-2026-26116

Q: What is the CVSS score of EUVD-2026-26116?

EUVD-2026-26116 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:N/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.1%.

| CVE-2026-41910 LOW

Incorrect Authorization (CWE-863)

2026-04-28 VulnCheck

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:N/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

3.1 LOW

Low-privilege auth required (PR:L); specific multi-channel ownership precondition maps CVSS 4.0 AT:P to AC:H; impact is integrity-only allowlist writes with unchanged scope.

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

4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/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 - 04:22 vuln.today

Analysis Generated

Jul 24, 2026 - 04:22 vuln.today

Severity Changed

Apr 28, 2026 - 19:52 NVD

MEDIUM LOW

CVSS changed

Apr 28, 2026 - 19:52 NVD

4.3 (MEDIUM) 2.3 (LOW)

EUVD ID Assigned

Apr 28, 2026 - 19:30 euvd

EUVD-2026-26116

Patch released

Apr 28, 2026 - 19:30 nvd

Patch available

CVE Published

Apr 28, 2026 - 18:10 nvd

LOW 2.3

DescriptionCVE.org

OpenClaw before 2026.4.8 omits owner-only enforcement for cross-channel allowlist writes in the /allowlist endpoint. An authorized non-owner sender can bypass access controls to perform allowlist modifications against different channels, violating the intended trust model.

AnalysisAI

Cross-channel allowlist write bypass in OpenClaw before 2026.4.8 allows an authorized but non-owner sender to modify the /allowlist endpoint of channels they do not own, violating the product's intended authorization model. The flaw is classified under CWE-863 (Incorrect Authorization) and is explicitly scoped by the vendor to OpenClaw's single-user local assistant trust model - the advisory excludes multi-tenant service boundaries. With a CVSS 4.0 score of 2.3, EPSS of 0.05% at the 16th percentile, SSVC exploitation status of none, and no public exploit code identified at time of analysis, this is a low-priority integrity-only issue warranting a normal patch cycle rather than emergency response.

Technical ContextAI

OpenClaw is a user-controlled local assistant distributed as the 'openclaw' npm package. The /allowlist endpoint governs which senders are permitted to interact with specific channels within the assistant. CWE-863 (Incorrect Authorization) describes the root cause: while the endpoint validates that the caller is an authorized sender, it omits the ownership check that should restrict cross-channel allowlist mutations to the channel owner only. This constitutes horizontal privilege escalation within the same authentication boundary - a legitimately credentialed non-owner principal can alter access controls on another channel's allowlist. The CPE string cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:* covers all openclaw npm releases prior to 2026.4.8. The CVSS 4.0 vector AT:P metric confirms a specific attack prerequisite: the existence of multiple channels with distinct ownership within the same instance must be present for cross-channel exploitation to be possible.

RemediationAI

Upgrade the openclaw npm package to version 2026.4.8 or later, as confirmed by the GHSA advisory GHSA-vc32-h5mq-453v and patch commit d7c3210cd6f5fdfdc1beff4c9541673e814354d5. The vendor states the fix was re-verified against main with targeted regression tests for the affected authorization boundary before publication. If immediate upgrade is not possible, restrict network access to the /allowlist endpoint to the channel owner only at the infrastructure level (e.g., reverse proxy ACLs or network policy), or disable cross-channel write capability if the deployment supports it - neither workaround addresses the missing authorization logic and may disrupt intended multi-channel workflows. Additional advisory context is available at https://www.vulncheck.com/advisories/openclaw-missing-owner-only-enforcement-in-allowlist-cross-channel-writes.