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

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

Openclaw CVE-2026-41298

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

CVE-2026-41298 has a CVSS 4.0 base score of 5.3 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/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%.

MEDIUM

Missing Authorization (CWE-862)

2026-04-21 disclosure@vulncheck.com

Authentication Bypass Openclaw

5.3

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.3 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch released

Apr 21, 2026 - 02:30 nvd

Patch available

Analysis Generated

Apr 21, 2026 - 00:39 vuln.today

Analysis Generated

Apr 21, 2026 - 00:22 vuln.today

CVE Published

Apr 21, 2026 - 00:16 nvd

MEDIUM 5.3

Blast Radius

ecosystem impact

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

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

Ecosystem-wide dependent count for version 2026.4.2.

DescriptionCVE.org

OpenClaw before 2026.4.2 fails to enforce write scopes on the POST /sessions/:sessionKey/kill endpoint in identity-bearing HTTP modes. Read-scoped callers can terminate running subagent sessions by sending requests to this endpoint, bypassing authorization controls.

AnalysisAI

OpenClaw before version 2026.4.2 fails to enforce write-scope authorization on the POST /sessions/:sessionKey/kill endpoint, allowing authenticated users with read-only credentials to terminate arbitrary subagent sessions. The vulnerability requires valid API credentials with read scope but does NOT require write permissions, enabling privilege escalation within identity-bearing authentication modes. No public exploit code has been identified, and this is not listed as actively exploited by CISA; however, the low CVSS score of 5.3 reflects the requirement for prior authentication rather than the ease of exploitation once credentials are obtained.

Technical ContextAI

OpenClaw is an agent orchestration platform that uses role-based access control (RBAC) with granular scopes (read versus write) to restrict API endpoint access. The vulnerability exists in the session management subsystem, specifically the POST /sessions/:sessionKey/kill endpoint, which is intended to terminate running subagent sessions. The root cause is a missing or improperly implemented authorization check (CWE-862: Missing Authorization) that validates whether the authenticated caller possesses write-level permissions before allowing session termination. In identity-bearing HTTP authentication modes, the platform correctly identifies the caller but fails to enforce scope boundaries, creating an authorization bypass. The affected versions do not verify that PR:L (authenticated user) also holds the necessary privilege level to invoke destructive operations, allowing read-scoped API tokens or users to perform write-class actions.

RemediationAI

Apply vendor-released patch by upgrading to OpenClaw version 2026.4.2 or later. This patch restores authorization scope enforcement on the POST /sessions/:sessionKey/kill endpoint, ensuring only authenticated users with explicit write permissions can terminate sessions. For organizations unable to immediately patch, implement network-level mitigations by restricting API access to trusted internal networks and auditing all API token assignments to remove unnecessary write-scope delegations - any API token or user with only read-scope access should be verified not to require session termination capabilities, reducing the attack surface. Additionally, enable detailed API audit logging on the /sessions/:sessionKey/kill endpoint to detect suspicious session termination attempts by read-scoped callers. These compensating controls do not eliminate the vulnerability but limit exposure until patching is feasible; they introduce no functional side effects if properly scoped to read-only credential holders who should not legitimately invoke this endpoint.