CVE-2026-100526: Vulnerability in discord
OpenClaw's Discord integration (npm package @openclaw/discord) before version 2026.9.3 could lose the sender-scoped media policy in the emoji and sticker upload actions before loading a local file. A sender permitted to invoke those actions could cause OpenClaw to read a host path that the same sender's configured media roots would otherwise reject, placing bytes from an out-of-policy local file into an outbound emoji or sticker upload. Exploitation requires access to the guild asset action and knowledge or derivation of a useful local path; the issue does not permit unrestricted filesystem browsing or code execution. The issue is fixed in @openclaw/discord 2026.9.3.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
@openclaw/discordto a version that resolves this vulnerability.Fixed in 2026.9.3
Event History
Frequently Asked Questions
Who is exposed to this issue?
OpenClaw deployments using @openclaw/discord before 2026.9.3 are exposed only where a sender is permitted to invoke the guild emoji or sticker upload actions. The sender must also know or be able to derive a useful local host path.
What can an attacker access through this flaw?
A permitted sender can cause bytes from a local file outside that sender's configured media roots to be included in an outbound emoji or sticker upload. The issue does not allow unrestricted filesystem browsing or code execution.
Is a default configuration known to be affected?
The available information does not state whether default configurations grant senders access to the guild asset actions. Exposure depends on whether those actions are available to the sender.
How can I remediate the issue?
Upgrade @openclaw/discord to version 2026.9.3. If an immediate upgrade is not possible, restrict access to the guild emoji and sticker upload actions for untrusted senders.