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

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

Openclaw CVE-2026-41300

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

CVE-2026-41300 has a CVSS 4.0 base score of 6.9 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/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

Incomplete Internal State Distinction (CWE-372)

2026-04-21 disclosure@vulncheck.com

Information Disclosure Openclaw

6.9

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

6.9 MEDIUM

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

None

User Interaction

Scope

Lifecycle Timeline

Patch released

Apr 21, 2026 - 02:30 nvd

Patch available

Analysis Generated

Apr 21, 2026 - 00:40 vuln.today

Analysis Generated

Apr 21, 2026 - 00:22 vuln.today

CVE Published

Apr 21, 2026 - 00:16 nvd

MEDIUM 6.9

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 trust-decline vulnerability that preserves attacker-discovered endpoints in remote onboarding flows. Attackers can route gateway credentials to malicious endpoints by having their discovered URL survive the trust decline process into manual prompts requiring operator acceptance.

AnalysisAI

OpenClaw before version 2026.3.31 fails to properly invalidate attacker-discovered endpoints during trust decline operations in remote onboarding workflows, allowing attackers to route gateway credentials to malicious endpoints by preserving their URLs through the trust decline process into manual operator acceptance prompts. The vulnerability requires user interaction (UI:A) but affects gateway credential confidentiality (VC:H), posing a significant risk to organizations using OpenClaw's remote onboarding feature with CVSS 6.9 (medium-high severity).

Technical ContextAI

OpenClaw is a remote onboarding and credential management platform that implements endpoint discovery and trust validation mechanisms. The vulnerability stems from improper handling of endpoint trust decisions in CWE-372 (Incomplete Internal State Distinction), where the application fails to adequately distinguish between trusted and untrusted states across different workflow phases. Specifically, when an operator declines trust for an attacker-discovered endpoint during the initial discovery phase, the application does not properly purge this endpoint from subsequent process flows. The endpoint URL persists into manual acceptance prompts, where operators may re-encounter and accept it without realizing it was previously rejected, creating a logical bypass of the trust validation mechanism. This affects OpenClaw's remote onboarding gateway credential management system across all versions before 2026.3.31.

RemediationAI

Upgrade OpenClaw to version 2026.3.31 or later, which properly invalidates attacker-discovered endpoints during trust decline operations and prevents them from persisting into subsequent approval prompts. The patch is available via the GitHub commit 2a75416634837c21ed05b8c3ed906eb7a7807060 and official release. Organizations unable to upgrade immediately should restrict remote onboarding operations to trusted, controlled network environments where endpoint discovery cannot be influenced by attackers, implement network segmentation to limit gateway credential exposure from onboarding flows, and mandate manual verification of endpoint URLs by operators before accepting them in approval prompts rather than relying on cached URL suggestions. These compensating controls reduce but do not eliminate risk, as they increase operational friction and depend on operator vigilance.