Skip to main content

Openclaw CVE-2026-35661

| EUVDEUVD-2026-21468 MEDIUM
Authentication Bypass Using an Alternate Path or Channel (CWE-288)
2026-04-10 VulnCheck
6.9
CVSS 4.0 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Alternate path authentication
Impact

CVSS 5.3 reflects a network-based attack with low complexity and no privileges required, but limited impact (integrity only, no confidentiality or availability loss). EPSS and KEV status are not provided in the input data. The attack vector is network-accessible and exploitable without user interaction (UI:N), making it remotely viable. However, the integrity impact is limited to session state modification rather than data exfiltration or service disruption. While the authorization bypass itself is severe from a design perspective, the actual real-world risk depends on what session mutations an attacker can perform and whether downstream controls mitigate this. The presence of a vendor patch indicates this was deemed actionable. Without EPSS score or KEV confirmation, this appears to be a moderate-priority issue for OpenClaw deployments using Telegram integration-urgent for DM-reliant workflows, but not critical for all users.

Exploit ScenarioDerived

An attacker sends a malicious Telegram callback query to an OpenClaw bot's direct message endpoint, crafting the callback data to modify session state (e.g., changing user settings, permissions, or session tokens) without providing proof of DM pairing. The weaker callback authorization logic accepts the mutation because it does not enforce the same pairing requirements as direct message commands, allowing state corruption. No public exploit code is independently confirmed in the provided references, but the attack requires only network access and knowledge of the Telegram bot API.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 10, 2026

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).

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.

Affected VersionsENISA

OpenClaw 0 <2026.3.25

Affected Packages

npm openclaw fix: 2026.3.25, 2026.3.28

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

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.

Know when Openclaw gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch released
Apr 10, 2026 - 16:30 nvd
Patch available
CVE Published
Apr 10, 2026 - 16:03 nvd
MEDIUM 6.9

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.

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.

Threat Intelligence Overview

EPSS Score
0.0%
Top 88% exploitable
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-28446 CRITICAL POC
9.4 Mar 05

Auth bypass in OpenClaw voice-call extension before 2026.2.1. EPSS 0.68%. PoC and patch available.

CVE-2026-33579 CRITICAL POC
9.4 Mar 31

Privilege escalation in OpenClaw (pre-2026.3.28) allows unauthenticated remote attackers to gain administrative access b

CVE-2026-32042 HIGH POC
8.8 Mar 21

OpenClaw versions 2026.2.22 through 2026.2.24 contain a privilege escalation vulnerability that allows authenticated att

CVE-2026-32051 HIGH POC
8.8 Mar 21

An authorization mismatch vulnerability in OpenClaw versions prior to 2026.3.1 allows authenticated users with operator.

CVE-2026-25253 HIGH POC
8.8 Feb 01

OpenClaw versions prior to 2026.1.29 automatically establish WebSocket connections to attacker-controlled gateway URLs e

CVE-2026-32846 HIGH POC
8.7 Mar 26

Path traversal in OpenClaw through version 2026.3.23 enables unauthenticated remote attackers to read arbitrary files in

CVE-2026-53857 HIGH POC
8.6 Jun 16

Authentication bypass in OpenClaw before 2026.5.3 allows remote attackers with low privileges to receive agent responses

CVE-2026-100530 HIGH POC
8.5 Sep 26

Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'a

CVE-2026-32064 HIGH POC
8.5 Mar 21

Unauthenticated access to the noVNC observer interface in OpenClaw's Docker sandbox browser allows anyone who can reach

CVE-2026-32055 HIGH POC
7.6 Mar 21

OpenClaw versions before 2026.2.26 allow authenticated attackers to write arbitrary files outside the workspace director

CVE-2026-32056 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a shell environment variable injection vulnerability in the system.run func

CVE-2026-32049 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.2.22 contain a resource exhaustion vulnerability where the application fails to consiste

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy