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

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

OpenClaw EUVD-2026-26100

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

EUVD-2026-26100 has a CVSS 4.0 base score of 5.4 (Medium). CVSS vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/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%.

| CVE-2026-41392 MEDIUM

Incomplete List of Disallowed Inputs (CWE-184)

2026-04-28 VulnCheck

Authentication Bypass Openclaw

5.4

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/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

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

Scope

Lifecycle Timeline

Analysis Generated

Apr 28, 2026 - 20:07 vuln.today

CVSS changed

Apr 28, 2026 - 19:52 NVD

6.7 (MEDIUM) 5.4 (MEDIUM)

EUVD ID Assigned

Apr 28, 2026 - 19:30 euvd

EUVD-2026-26100

Analysis Generated

Apr 28, 2026 - 19:30 vuln.today

Patch released

Apr 28, 2026 - 19:30 nvd

Patch available

CVE Published

Apr 28, 2026 - 18:09 nvd

MEDIUM 5.4

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 exec allowlist bypass vulnerability allowing attackers to inherit allowlist trust via shell init-file wrapper invocations. Attackers can exploit shell options like --rcfile, --init-file, and --startup-file to load attacker-chosen initialization files while bypassing exec allowlist matching restrictions.

AnalysisAI

OpenClaw before version 2026.3.31 allows local authenticated users with user interaction to bypass exec allowlist restrictions via shell initialization file options (--rcfile, --init-file, --startup-file), enabling them to load attacker-controlled initialization files and achieve high-impact unauthorized access to confined resources. Exploitation requires local access, low privileges, user interaction, and specific timing conditions, but bypasses a critical security control intended to restrict executable trust.

Technical ContextAI

OpenClaw implements an allowlist-based execution control mechanism to restrict which binaries and resources can be executed within its confined environment. The vulnerability exploits CWE-184 (Incomplete List of Disallowed Inputs), a logic bypass where shell invocation options commonly used for initialization file loading are not properly filtered or validated by the allowlist matching logic. Attackers can chain shell options like --rcfile (bash), --init-file (bash), or --startup-file (zsh) to specify alternate initialization files, which are then sourced with the trust level inherited from the allowlisted shell binary itself, circumventing per-file allowlist checks. The CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:* indicates all versions before 2026.3.31 are affected.

RemediationAI

Upgrade OpenClaw to version 2026.3.31 or later, which patches the allowlist bypass by properly validating and filtering shell initialization file options before exec invocation. The upstream fix is available in commit 0c8375424620e12777ef24c162eedc7e9fcfd7e3 (https://github.com/openclaw/openclaw/commit/0c8375424620e12777ef24c162eedc7e9fcfd7e3). If immediate upgrade is not possible, implement compensating controls: restrict shell invocation within OpenClaw confinement boundaries to setups that do not expose shell options (e.g., use shell in non-interactive mode or via wrapper scripts that strip user-supplied flags), or disable shell-based initialization file loading entirely if not required for legitimate workflows. Be aware that disabling shell initialization may break legitimate scripts that depend on these features, requiring workflow testing before deployment.