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

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

OpenClaw CVE-2026-41340

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

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

Q: Which versions of OpenClaw are affected by CVE-2026-41340?

OpenClaw's Telegram legacy `allowFrom` migration incorrectly propagates default-account trust to all configured named Telegram accounts in npm package versions through 2026.3.28, enabling Telegram…. A patch is available.

EUVD-2026-25324 MEDIUM

Incomplete Internal State Distinction (CWE-372)

2026-04-23 VulnCheck

GHSA-q85g-cf2c-5gq6

Authentication Bypass Openclaw

6.3

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

6.3 MEDIUM

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

vuln.today AI

4.2 MEDIUM

AC:H reflects required migration pre-conditions and multi-account configuration; PR:L reflects attacker's required prior trust in the default-account allowFrom store; C:L/I:L bound to Telegram channel scope with no availability impact.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 03:28 vuln.today

Analysis Generated

Jul 24, 2026 - 03:28 vuln.today

CVSS changed

Apr 23, 2026 - 22:28 NVD

6.5 (MEDIUM) 6.3 (MEDIUM)

EUVD ID Assigned

Apr 23, 2026 - 22:15 euvd

EUVD-2026-25324

Patch released

Apr 23, 2026 - 22:15 nvd

Patch available

CVE Published

Apr 23, 2026 - 21:57 nvd

MEDIUM 6.3

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 authentication boundary vulnerability where Telegram legacy allowFrom migration incorrectly fans default-account trust into all named accounts. Attackers can exploit this trust propagation to bypass authentication controls and gain unauthorized access to named accounts.

AnalysisAI

OpenClaw's Telegram legacy allowFrom migration incorrectly propagates default-account trust to all configured named Telegram accounts in npm package versions through 2026.3.28, enabling Telegram users previously trusted only on the default account to bypass authentication controls and interact with named accounts they were never explicitly authorized to access. The vendor-confirmed fix is present in version 2026.3.31, released 2026-03-31. No public exploit exists; EPSS is 0.06% and CISA SSVC records exploitation as none at time of analysis.

Technical ContextAI

OpenClaw is an npm package (CPE: cpe:2.3:a:openclaw:openclaw) providing Telegram bot channel integration with multi-account support. The doctor command runs detectLegacyStateMigrations() in src/infra/state-migrations.ts to upgrade stored state when deploying new configurations. In the vulnerable code path, the migration used listTelegramAccountIds() to enumerate every configured named Telegram account and copied the legacy pairingAllowFrom trust store to each one. The pairingAllowFrom store controls which Telegram principals are authorized to interact with an account. CWE-372 (Incomplete Internal State Distinguished) applies precisely: the migration logic conflated the trust boundary of the default account with those of all named accounts, treating every account as an equivalent trust recipient. The fix in commit d8c68c8d replaces the fan-out call with resolveDefaultTelegramAccountId(), scoping trust migration only to the designated default account.

RemediationAI

Upgrade the openclaw npm package to version 2026.3.31 or later; this is a confirmed released version containing fix commit d8c68c8d4265ea6fa5e8c5e056534c351bddef37. Run npm install openclaw@2026.3.31 (or the equivalent lockfile update) and re-run the doctor migration after upgrading so the corrected migration logic executes. Details are available in the GitHub Security Advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-f693-58pc-2gfr. If immediate upgrade is not possible, avoid executing the doctor migration command until the package is updated; this prevents the trust fan-out from occurring but leaves the system in a legacy state and may block other state-dependent features. A secondary compensating control is to minimize the principals in the legacy pairingAllowFrom trust list for the default account, reducing the set of users who could benefit from the erroneous propagation - though this requires manual list curation and does not eliminate the boundary bug itself.