dbcve.org
OpenclawApplication

CVE-2026-41367

MEDIUM · 5.0 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 2026.3.28 or later.
See remediation →
56/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 versions 2026.2.14 through 2026.3.24 fail to consistently apply guild and channel policy gates to Discord button and component interactions. Attackers can trigger privileged component actions from blocked contexts by bypassing channel policy enforcement.

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 · high confidence

OpenClaw versions 2026.2.14-2026.3.24 fail to enforce guild and channel policy gates on Discord button and component interactions. When users interact with buttons or other components, the code bypasses the authorization checks that would normally restrict actions based on channel or guild permissions, allowing attackers in blocked contexts to trigger privileged actions.

MitigationImplement consistent policy gate enforcement for all Discord interaction types (buttons, selects, modals). Add explicit channel and guild permission validation before processing any component interaction, ensuring the same authorization checks used elsewhere in the application are applied uniformly.

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.2.14, < 2026.3.28

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
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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 'openclaw --version' or check the package.json/version file in the OpenClaw installation directory
    Affected if Version is 2026.2.14 or higher but lower than 2026.3.28
  2. Identify Discord component interaction handlers
    Search the codebase for event handlers listening to 'interactionCreate' or 'componentInteraction' events, typically in handlers/ or events/ directories
    Affected if Component interaction handlers exist and handle button clicks or other Discord components
  3. Examine policy validation in component handlers
    Open the component interaction handler files and search for guild or channel permission/policy validation logic (look for 'channelPermissions', 'guildPolicies', or similar validation functions before action execution)
    Affected if Component handlers execute privileged actions without first validating that the interaction originated from an allowed channel or guild per configured policies

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.28 or later
Fixed in 2026.3.28
Interim mitigation

Implement consistent policy gate enforcement for all Discord interaction types (buttons, selects, modals). Add explicit channel and guild permission validation before processing any component interaction, ensuring the same authorization checks used elsewhere in the application are applied uniformly.

Recommended fix Moderate confidence

2026.3.28

  1. Identify the current OpenClaw version by checking the installation or running 'openclaw --version'
  2. Stop the OpenClaw service to prevent any active sessions during upgrade
  3. Backup the current OpenClaw configuration directory (commonly /etc/openclaw or the config path used in your deployment)
  4. Upgrade OpenClaw to version 2026.3.28 or later using your package manager or deployment method (e.g., 'pip install --upgrade openclaw' or your container orchestration tool)
  5. Verify the new version is installed: 'openclaw --version'
  6. Restart the OpenClaw service
  7. Test that Discord button and component interactions now properly enforce guild and channel policy gates

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41367 — 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-41367 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