dbcve.org
OpenclawApplication

CVE-2026-53849

HIGH · 8.1 CVSS v3.1 Published 2026-06-16
Fix available
A fix is available. Upgrade to 2026.5.7 or later.
See remediation →
87/100
Remediation priority · High
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.5.7 contains a privilege escalation vulnerability where the allowFrom feature improperly validates Discord account identity using mutable display names instead of immutable user IDs. Attackers with Discord accounts can change their display name to match a policy entry and gain unauthorized agent access intended for another Discord identity.

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

The allowFrom feature in OpenClaw validates Discord user identity by checking mutable display names rather than immutable Discord user IDs. An attacker with a Discord account can change their display name to match a policy entry and bypass authentication to gain agent access intended for another Discord identity.

MitigationUpdate the allowFrom feature to validate against immutable Discord user IDs (snowflake IDs) instead of display names, and migrate existing policies to use user IDs. Upgrade to OpenClaw 2026.5.7 or later.

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.5.7= 2026.5.7

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify OpenClaw version
    Locate and inspect the installed OpenClaw version information, typically available via CLI version flag, config file, or package metadata
    Affected if version is less than 2026.5.7 or exactly 2026.5.7
  2. Locate allowFrom policy configuration
    Find the policy configuration file or database entries that define allowFrom rules for Discord agent access control
    Affected if allowFrom policies exist and reference Discord identities
  3. Inspect allowFrom identity references
    Examine the policy entries to determine whether they store Discord display names (mutable) or Discord user IDs (snowflake IDs) as the identity attribute
    Affected if policies use display names rather than immutable user IDs for identity matching
  4. Verify allowFrom feature is active
    Check if the allowFrom feature is enabled in the OpenClaw configuration and actively being used to control agent access
    Affected if allowFrom is enabled and processing authentication requests

You are affected if OpenClaw version is < 2026.5.7 or = 2026.5.7 AND the allowFrom feature is configured with display names instead of immutable Discord user IDs.

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.5.7 or later
Fixed in 2026.5.7
Interim mitigation

Update the allowFrom feature to validate against immutable Discord user IDs (snowflake IDs) instead of display names, and migrate existing policies to use user IDs. Upgrade to OpenClaw 2026.5.7 or later.

Recommended fix High confidence

2026.5.8 or later

  1. Upgrade OpenClaw to version 2026.5.8 or later
  2. After upgrading, verify that the allowFrom feature now uses immutable Discord user IDs instead of mutable display names
  3. Review existing allowFrom policies to confirm they reference Discord user IDs rather than display names
  4. Test the authentication flow to confirm the vulnerability is remediated
  5. Ensure any new allowFrom policies are created using Discord user IDs (not display names)
Caveat Administrators will need to update existing allowFrom policies to use Discord user IDs instead of display names, as display name-based policies will no longer work

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA1.0 h
13.0 hours of engineering $2,260
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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