AI agent vulnerability · OpenClaw

CVE-2026-27484: OpenClaw Discord moderation authorization used untrusted sender identity in tool-driven flows

lowCVSS 4.0 2.3GHSA-wh94-p5m6-mr7j

Overview Discord moderation action handling (timeout, kick, ban) used sender identity from request parameters in tool-driven flows, instead of trusted runtime sender context. Impact In setups where Discord moderation actions are enabled and the bot has the necessary guild permissions, a non-admin user could request moderation actions by spoofing sender identity fields.

Published Feb 20, 2026 · Updated Feb 23, 2026

Affected packages

openclaw

Ecosystem: npm
Affected: < 2026.2.18
Fixed in: 2026.2.18
Check: npm ls openclaw

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Overview

Discord moderation action handling (timeout, kick, ban) used sender identity from request parameters in tool-driven flows, instead of trusted runtime sender context.

Impact

In setups where Discord moderation actions are enabled and the bot has the necessary guild permissions, a non-admin user could request moderation actions by spoofing sender identity fields.

Affected Packages / Versions

Package: openclaw (npm)
Latest published affected version (as of 2026-02-19): 2026.2.17
Affected range: <=2026.2.17
Fixed in planned next release: 2026.2.18

Fix

Moderation authorization now uses trusted sender context (requesterSenderId) instead of untrusted action params.
Added permission checks for required guild capabilities per action.

Fix Commit(s)

775816035ecc6bb243843f8000c9a58ff609e32d

Thanks @aether-ai-agent for reporting.

Credited to aether-ai-agent.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries