dbcve.org
OpenclawApplication

CVE-2026-32923

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-29
Fix available
A fix is available. Upgrade to 2026.3.11 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenClaw before 2026.3.11 contains an authorization bypass vulnerability in Discord guild reaction ingestion that fails to enforce member users and roles allowlist checks. Non-allowlisted guild members can trigger reaction events accepted as trusted system events, injecting reaction text into downstream session context.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OpenClaw before 2026.3.11 fails to validate that Discord guild members triggering reactions are on an authorized users/roles allowlist. The reaction ingestion handler accepts these events as trusted system events without proper authorization checks, allowing non-allowlisted members to inject arbitrary reaction text into downstream session context.

MitigationImplement and enforce user/role allowlist validation in the Discord reaction event handler to verify the reacting member is authorized before accepting the reaction as a trusted event.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenclawApplication
Affected:< 2026.3.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed OpenClaw version
    Run the version command for OpenClaw (typically openclaw --version or check package.json/package.toml for the installed version)
    Affected if The installed version is less than 2026.3.11
  2. Verify Discord integration is enabled
    Inspect the OpenClaw configuration files for Discord-related settings (look for discord, webhook, or reaction_handler keys)
    Affected if Discord integration or reaction handling is enabled in the configuration
  3. Check for allowlist configuration
    Search for allowlist, whitelist, or authorized_users/roles configuration in OpenClaw config files or environment variables related to Discord
    Affected if No allowlist is configured or the allowlist is empty/unenforced for Discord reaction events
  4. Inspect reaction event handler logs
    Review OpenClaw application logs for Discord reaction events and check if authorization validation is occurring
    Affected if Reaction events from non-allowlisted users are being processed without rejection logs

You are affected if OpenClaw version is below 2026.3.11 and Discord reaction handling is enabled without a properly configured allowlist validation mechanism.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.3.11 or later
Fixed in 2026.3.11
Interim mitigation

Implement and enforce user/role allowlist validation in the Discord reaction event handler to verify the reacting member is authorized before accepting the reaction as a trusted event.

Recommended fix Moderate confidence

2026.3.11

  1. Identify the current OpenClaw version running in your environment by checking the application startup logs or version endpoint
  2. Backup your current OpenClaw configuration, database, and any custom settings
  3. Upgrade OpenClaw to version 2026.3.11 or later by pulling the updated container image or using your deployment method (e.g., docker pull, helm upgrade)
  4. Restart the OpenClaw service to apply the updated version
  5. Verify the upgrade was successful by checking the running version matches 2026.3.11 or later
  6. Test the Discord guild reaction functionality to confirm that non-allowlisted members can no longer inject reaction text into session context

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32923 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32923 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data