Skip to main content

OpenClaw Feishu CVE-2026-100540

| EUVDEUVD-2026-87510 HIGH
Incorrect Authorization (CWE-863)
2026-09-26 VulnCheck GHSA-77rw-6qrm-8q2v
7.6
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged access to OpenClaw agent
  2. Delivery
    Trigger Feishu model tool operation
  3. Exploit
    Default-account selection skips disabled check
  4. Execution
    Operation runs as revoked identity
  5. Impact
    Read or modify Feishu resources

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a multi-account OpenClaw Feishu configuration in which the operator has disabled the default account but that account's Feishu credentials remain stored/valid. The attacker must already hold low-privilege access sufficient to invoke the agent's model tool operations (PR:L), and exploitation is gated by the compound precondition reflected in AC:H/AT:P - a single-account or credential-purged deployment is not affected. No end-user interaction is required (UI:N). Limiting factors: this is a non-default operational state (disabled-yet-credentialed default account) and requires pre-existing authenticated access to the OpenClaw agent, so it is not exploitable by an anonymous remote attacker against a default install.

Impact

This is a genuine but conditional authorization flaw (CWE-863), not a high-CVSS-but-hollow finding. The vendor CVSS4 vector (7.6, AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N) is internally consistent with the description: network-reachable, but with high complexity (AC:H) and an attack requirement (AT:P) reflecting the specific precondition - a multi-account OpenClaw Feishu deployment where a disabled default account still retains valid credentials. PR:L confirms the actor already holds some legitimate access to the OpenClaw agent/Gateway; this is not an unauthenticated internet-facing bug. No EPSS score, no CISA KEV listing, and no public POC are present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The realistic priority is moderate: impact is high on confidentiality and integrity of Feishu resources (read/modify through a revoked identity), but exploitation is gated behind a specific non-default multi-account configuration and prior low-privilege access, which is why AC:H/AT:P is appropriate. My independent 3.1 scoring (~6.5) is slightly lower than the vendor's 4.0 rating, driven mainly by VA:N (no availability impact) and the compound configuration prerequisite. No signals conflict; the main gap is the absence of exploitation-probability telemetry (EPSS).

Exploit ScenarioDerived

In an OpenClaw deployment integrated with Feishu using multiple accounts, an operator disables the default account (e.g., to revoke a former employee or compromised identity) but its stored credentials are not purged. A low-privileged actor who can drive the agent's model tool operations triggers Feishu resource actions; because the code never checks the disabled flag before selecting the default account, the operations execute under the revoked identity, allowing reads or modifications the actor should no longer be able to perform. No public exploit code is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 26, 2026

Incorrect authorization in OpenClaw Feishu before 2026.8.1 allows an authenticated attacker who can already invoke the agent's model tool operations to act through a default account that the operator has disabled, because the account-selection logic never checks the disabled flag before using that account's still-stored Feishu credentials. Successful exploitation lets the attacker read or modify Feishu resources under a revoked identity, yielding high confidentiality and integrity impact (CVSS 4.0 base 7.6; assessed CVSS 3.1 7.6 with AV:N/AC:H/PR:L/UI:N/C:H/I:H/A:N by our analysis). Exploitation is conditional and non-default: it requires a multi-account configuration where the default account is disabled yet its credentials remain valid, plus pre-existing low-privilege access to the OpenClaw agent, so it is not reachable by an anonymous remote attacker against a default install; no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV).

RemediationAI

Vendor-released patch: upgrade OpenClaw Feishu to 2026.8.1 or later, which restores the disabled-account state check before the default account is selected for model tool operations; the fix is published under advisory GHSA-h2qg-fxpv-82v6 at https://github.com/openclaw/openclaw/security/advisories/GHSA-h2qg-fxpv-82v6. If immediate upgrade is not possible, the highest-value compensating control is to eliminate the enabling precondition rather than the payload: purge or revoke the Feishu credentials (app secret, tenant/user tokens) of any disabled account so the selection routine has nothing usable to fall back on, at the cost of requiring the operator to re-authenticate and re-provision when that account is re-enabled. Alternatively, collapse the deployment to a single active account on releases where a second account is not required, which removes the multi-account code path entirely but reduces functional flexibility for teams that separate workloads across accounts. Where multi-account operation is mandatory, restrict invocation of model tool operations to a narrowly scoped set of trusted operators (the assessed vector requires PR:L, so shrinking that low-privilege population directly removes the attack prerequisite), and monitor Feishu audit logs for API calls attributed to accounts that are administratively marked disabled, since such activity is a reliable indicator of this flaw being exercised. Neither credential purging nor access restriction carries residual exposure to the Feishu resources themselves, but both are operational workarounds and should be replaced by the 2026.8.1 upgrade once testing permits.

Affected VersionsENISA

feishu 0 <2026.8.1

Affected Packages

euvd feishu fix: 2026.8.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

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

Technical ContextAI · show details

The flaw is rooted in CWE-863 (Incorrect Authorization): OpenClaw's Feishu integration maintains multiple account configurations, one of which is designated the default, and its model tool operations resolve an account for outbound Feishu API calls without validating the account's disabled/enabled state. When an operator disables the default account but the underlying Feishu credentials (app ID/secret or tenant tokens) remain stored and valid, the selection routine still picks that account, so authorization decisions are made against an identity the operator intended to revoke. The result is a logic-level authentication/authorization bypass in the account-resolution layer rather than a memory-safety or injection defect. This is reflected in the CPE cpe:2.3:a:openclaw:feishu:*:*:*:*:*:*:*:* covering all releases before 2026.8.1, and by the assessed vector's AC:H/AT:P (high attack complexity with a pre-existing compound precondition) combined with PR:L and UI:N: the attacker must first hold low-privilege access sufficient to drive the agent's tool invocations, after which the account check is skipped without any victim interaction. The vendor's advisory is published as GHSA-h2qg-fxpv-82v6, with additional detail in VulnCheck's advisory.

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

Vendor (VulnCheck) PRIMARY 7.6 HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.8 MEDIUM

PR:L because the actor must already drive the agent; AC:H for the multi-account disabled-but-credentialed precondition; C:H/I:H for read/modify of Feishu resources; A:N as no availability impact is described.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

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

Lifecycle Timeline

2
Patch available
Sep 26, 2026 - 03:01 EUVD
CVE Published
Sep 26, 2026 - 02:18 cve.org
HIGH 7.6

DescriptionCVE.org

OpenClaw Feishu before 2026.8.1 fails to validate whether a configured default account is disabled before selecting it for model tool operations. Attackers can exploit multi-account setups where a disabled default account retains credentials to read or modify Feishu resources through a revoked identity.

Technical POC Analysis

Evidence base: GHSA-h2qg-fxpv-82v6 only.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

A high-severity authorization flaw in OpenClaw Feishu (versions before 2026.8.1) would allow an attacker who already holds low-privilege access to the OpenClaw agent to operate through a Feishu account the organization believes it has disabled, reading or altering Feishu content under a revoked identity. Exposure is limited to environments running multiple Feishu accounts where the default account is disabled but its credentials are still stored - a non-default configuration - so leadership should focus on confirming whether any team matches that profile. Where it does, the flaw undermines the trust placed in account deactivation, which is a core access-control assurance the business relies on.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Low
niche open-source AI agent framework Feishu integration plugin, limited production footprint
Data Quality
6 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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0
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-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

CVE-2026-32048 HIGH POC
7.5 Mar 21

OpenClaw versions prior to 2026.3.1 contain a sandbox escape vulnerability that allows authenticated attackers with low

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