GHSA-2q7j-2vhx-56g8: High severity npm/@openclaw/feishu vulnerability
Summary
Feishu tools could ignore per-account disablement. In affected versions, a lower-trust caller or configured input path could perform actions that should have required a stronger authorization or policy check.
This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.
Impact
When the affected feature is enabled and reachable, this could perform actions that should have required a stronger authorization or policy check. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.
Patched Versions
The first stable patched version is 2026.6.9.
Mitigations
Upgrade to a patched OpenClaw release when one is listed. Before upgrading, restrict the affected feature to trusted operators or disable it when it is not needed. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@openclaw/feishuto a version that resolves this vulnerability.Fixed in 2026.6.9 - Upgrade
Upgrade
OpenClawto a version that resolves this vulnerability.Fixed in 2026.6.9 - Configuration
Disable the affected feature when it is not needed (especially when it is enabled and reachable by lower-trust callers).
OpenClaw (affected feature) affected feature = disabled - Compensating control
Restrict the affected feature to trusted operators before upgrading; do not allow lower-trust callers to reach the configured input path that performs those actions.
- Compensating control
Avoid sharing one Gateway between mutually untrusted users to prevent lower-trust access paths from reaching trusted execution surfaces.
- Compensating control
Keep channel and tool allowlists narrow (limit which channels/tools are permitted) as part of general hardening.
Event History
Frequently Asked Questions
Which deployments are most exposed?
Deployments are most exposed when the Feishu feature is enabled and reachable by a lower-trust caller or configured input path. Risk depends on whether that path can invoke actions that should require stronger authorization or policy checks.
What must an attacker or untrusted user be able to do?
They need access to a lower-trust caller or input path that can reach the affected enabled feature. No user interaction is required, but practical exploitation depends on the operator's configuration and reachable inputs.
What version contains the first stable fix?
The first stable patched OpenClaw version is 2026.6.9.
What can be done before upgrading?
Restrict the affected feature to trusted operators or disable it if it is not needed. Keep channel and tool allowlists narrow, avoid sharing a Gateway among mutually untrusted users, and disable the affected feature when lower-trust inputs could reach it.
How should teams assess whether they are affected?
Check whether the Feishu feature is enabled, whether it is reachable, and whether lower-trust callers or configured input paths can invoke it. Also identify workflows that rely on per-account disablement to prevent actions, since that disablement could be ignored.