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

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

Openclaw CVE-2026-35661

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

CVE-2026-35661 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: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.0%.

EUVD-2026-21468 MEDIUM

Authentication Bypass Using an Alternate Path or Channel (CWE-288)

2026-04-10 VulnCheck

Authentication Bypass 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: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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

EUVD ID Assigned

Apr 10, 2026 - 16:30 euvd

EUVD-2026-21468

Analysis Generated

Apr 10, 2026 - 16:30 vuln.today

Patch released

Apr 10, 2026 - 16:30 nvd

Patch available

CVE Published

Apr 10, 2026 - 16:03 nvd

MEDIUM 6.9

Blast Radius

ecosystem impact

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

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

Ecosystem-wide dependent count for version 2026.3.28.

DescriptionCVE.org

OpenClaw before 2026.3.25 contains an authorization bypass vulnerability in Telegram callback query handling that allows attackers to mutate session state without satisfying normal DM pairing requirements. Remote attackers can exploit weaker callback-only authorization in direct messages to bypass DM pairing and modify session state.

AnalysisAI

OpenClaw before 2026.3.25 allows remote attackers to bypass Telegram direct message pairing requirements and mutate session state through weaker callback-only authorization mechanisms. An unauthenticated attacker can craft malicious Telegram callback queries in direct messages to modify session state without satisfying the normal DM pairing security controls, resulting in unauthorized state modification with CVSS 5.3 (medium severity).

Technical ContextAI

OpenClaw's Telegram integration implements callback query handling for direct message interactions. The vulnerability stems from improper authorization checks (CWE-288: Improper Authentication) in the callback query processing logic for Telegram DMs. The vulnerability allows attackers to exploit a weaker authorization model in callback-only flows compared to the standard DM pairing mechanism, which normally requires mutual authentication handshakes. The affected product is the OpenClaw application (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*), which integrates with Telegram's bot API for direct message functionality. The root cause is insufficient validation of callback query origins and session binding in direct message contexts, permitting state mutations that should be restricted to authenticated paired users.

RemediationAI

Vendor-released patch: upgrade OpenClaw to version 2026.3.25 or later. The upstream fix is available via commit 269282ac69ab6030d5f30d04822668f607f13065 at https://github.com/openclaw/openclaw/commit/269282ac69ab6030d5f30d04822668f607f13065. Administrators should prioritize this update for OpenClaw instances accepting Telegram direct message callbacks. Until patched, consider disabling Telegram DM callback handling or implementing additional callback origin validation at the application boundary if an immediate upgrade is not feasible.