CVE-2026-53835: OpenClaw Feishu Dynamic-Agent Binding Authorization Bypass
OpenClaw versions before 2026.5.6 have a flaw in how they enforce configuration rules for Feishu dynamic-agent bindings. An authenticated user can create or modify these bindings while bypassing the normal access controls that should restrict who can make such changes. This means someone with legitimate credentials could potentially create unauthorized connections between senders and agents that policy should have blocked.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 4.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Weaknesses (CWE)
- CWE-863
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-12 / 2026-06-17
NVD description (verbatim)
OpenClaw before 2026.5.6 contains a configuration enforcement bypass vulnerability in Feishu dynamic-agent bindings that allows authenticated senders to create or update bindings without honoring configured config-write controls. Attackers can exploit this by leveraging the dynamic-agent binding feature to change sender-agent binding state beyond intended policy, potentially enabling unauthorized binding modifications.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-53835 is an authorization bypass vulnerability (CWE-863: Improper Authorization) affecting OpenClaw's Feishu dynamic-agent binding mechanism. The vulnerability exists because the application fails to properly enforce config-write access controls when processing binding creation or update requests from authenticated users. An attacker who holds valid credentials can circumvent intended policy enforcement to modify sender-agent binding state, effectively bypassing authorization checks that ordinarily govern binding lifecycle operations.
Business impact
This vulnerability creates a compliance and operational risk for organizations using OpenClaw with Feishu integrations. Unauthorized binding modifications could allow insiders or compromised accounts to establish unapproved sender-agent communication paths, potentially enabling data exfiltration, unauthorized integrations, or policy circumvention without triggering expected audit controls. The impact is amplified in environments where role-based access controls are central to data governance or regulatory compliance.
Affected systems
OpenClaw versions prior to 2026.5.6 are affected. The vulnerability specifically targets the Feishu dynamic-agent binding feature; organizations using this integration should prioritize assessment. The flaw requires an attacker to hold valid authentication credentials, so the exposure is limited to authenticated users but still represents a significant insider risk vector.
Exploitability
The vulnerability has a CVSS v3.1 base score of 4.3 (MEDIUM severity) with a network-accessible vector (AV:N), low attack complexity (AC:L), and a requirement for low privilege (PR:L). No user interaction is needed (UI:N). While the score is moderate, the lack of elevation from a typical user role and the simplicity of exploitation via standard API calls make this practically exploitable by any authenticated user without special privileges. The vulnerability is not currently tracked in CISA's Known Exploited Vulnerabilities catalog.
Remediation
Upgrade OpenClaw to version 2026.5.6 or later to apply the authorization enforcement fix. Verify the patch version against the official vendor advisory prior to deployment. Organizations should also audit existing Feistel dynamic-agent bindings to detect any unauthorized or unexpected sender-agent relationships created while running vulnerable versions.
Patch guidance
Apply OpenClaw 2026.5.6 or newer in a controlled manner, testing in a non-production environment first to confirm compatibility with your Feishu integration configuration. Because this is an authentication and authorization control fix, it should be prioritized for prompt deployment. Verify patch integrity and test binding creation/modification workflows post-update to confirm proper enforcement of config-write policies.
Detection guidance
Monitor OpenClaw audit logs for unexpected dynamic-agent binding creation or modification events, particularly those initiated by user accounts with limited expected privilege levels. Search for binding updates that correlate with policy-restricted accounts or out-of-band user activities. Network monitoring can flag unusual Feishu API calls from your OpenClaw infrastructure. Consider implementing additional logging on binding lifecycle operations if not already present.
Why prioritize this
Although the CVSS score is moderate (4.3), this vulnerability directly undermines access control enforcement—a critical security function. The requirement for valid credentials limits random external exploitation but increases insider risk and the likelihood of abuse by compromised service accounts. For organizations where Feishu integration handles sensitive workflows or where policy enforcement is compliance-critical, this warrants prompt attention despite the moderate base score.
Risk score, explained
The CVSS v3.1 score of 4.3 reflects the availability of a network vector and low complexity, offset by the requirement for prior authentication. The impact is limited to integrity (I:L)—unauthorized binding modifications—with no confidentiality or availability impact. However, the real-world risk is elevated by the ease of exploitation and the sensitivity of what authorization bypass enables: circumventing intended policy controls. Organizations should weight this higher if Feishu bindings are central to data governance.
Frequently asked questions
Do I need valid credentials to exploit this?
Yes. The vulnerability requires authenticated access (PR:L). This means only users or service accounts with valid OpenClaw credentials can exploit it, which limits the exposure but does not eliminate it. A compromised user account or insider could abuse this flaw.
Is there active exploitation in the wild?
As of the publication date (June 12, 2026), CVE-2026-53835 is not listed in CISA's Known Exploited Vulnerabilities catalog, suggesting no widespread active exploitation has been reported. However, the low complexity and straightforward nature of the attack mean exploitation is feasible once the vulnerability is publicly known.
How should I prioritize this among other patches?
Prioritize based on your use of Feishu integrations and the sensitivity of binding operations in your environment. If dynamic-agent bindings control access to sensitive data or systems, treat this as a high-priority update. If Feishu integration is peripheral, it can be included in a regular patching cycle, but avoid extending delay beyond standard update windows.
What should I look for to detect if I was compromised by this vulnerability?
Review dynamic-agent binding logs and audit records for unexpected binding creations or modifications, especially by non-administrative accounts or service accounts outside their normal operation scope. Compare current bindings against your baseline configuration to identify unintended sender-agent relationships. Correlate timing with user activities and access logs.
This analysis is based on CVE-2026-53835 as published and modified through June 17, 2026. No exploit code or weaponized proof-of-concept is provided. Organizations should verify patch availability and version numbers directly with the OpenClaw vendor advisory before implementing. Risk assessment should account for your specific environment, Feishu integration scope, and regulatory obligations. This document is for informational purposes and does not constitute professional security advice or a substitute for vendor guidance. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-32906MEDIUMOpenClaw Privilege Escalation in Slack Plugin Approvals
- CVE-2026-34507MEDIUMOpenClaw QQBot Admin Command Policy Bypass (CVSS 5.4)
- CVE-2026-35673MEDIUMOpenClaw SSRF Policy Bypass in Debug and Export Routes
- CVE-2026-53808MEDIUMOpenClaw Approval Policy Bypass in Skill Workshop Apply Flow
- CVE-2026-53854MEDIUMOpenClaw Privilege Escalation via Cross-Channel Command Authorization Bypass
- CVE-2026-53860MEDIUMOpenClaw Sender Policy Bypass in BlueBubbles
- CVE-2026-35674HIGHOpenClaw Gateway Scope Bypass Privilege Escalation
- CVE-2026-53807HIGHOpenClaw Telegram Authorization Bypass (CVSS 8.8)