OpenclawApplication

CVE-2026-53818

MEDIUM · 6.6 CVSS v3.1 Published 2026-06-11

Fix available

A fix is available. Upgrade to 2026.4.24 or later.

See remediation →

68/100

Remediation priority · Elevated

Zero-click

Official description

NVD · unedited

OpenClaw before 2026.4.24 contains an authorization bypass vulnerability in the MCP loopback feature that allows non-owner callers to skip owner-only tool policies and before-tool-call hooks. Attackers can invoke owner-only behavior through the affected loopback path to execute restricted tools when the feature is enabled and reachable.

Technical summary

dbcve analysis · moderate confidence

OpenClaw before version 2026.4.24 has an authorization bypass in the MCP loopback feature. The vulnerability allows non-owner callers to circumvent owner-only tool policies and before-tool-call hooks by invoking restricted tools through the affected loopback path when the feature is enabled and accessible.

MitigationUpgrade OpenClaw to version 2026.4.24 or later to obtain the patched code. If immediate upgrading is not feasible, disable the MCP loopback feature as a temporary workaround until the upgrade can be completed.

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

Affected products & versions

NVD · CPE data

OpenclawApplication

Affected:< 2026.4.24

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
Availability: Low

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

Am I affected?

dbcve checks

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

Identify OpenClaw version

Run the command to retrieve the installed OpenClaw version (for example, openclaw --version or check the package manifest)

Affected if The installed version is earlier than 2026.4.24
Locate MCP loopback configuration

Search the OpenClaw configuration files for settings related to MCP loopback or loopback features (common paths may include config/ or settings files)

Affected if MCP loopback is explicitly enabled in the configuration
Verify loopback accessibility

Inspect network or service configuration to determine if the MCP loopback endpoint is exposed or accessible to non-owner callers (check binding addresses, firewall rules, or access controls)

Affected if The loopback feature is enabled and reachable by unauthenticated or non-owner users
Review tool access logs

Examine OpenClaw audit or access logs for any invocations of owner-restricted tools originating from the loopback path by non-owner principals

Affected if Such bypass attempts appear in the logs

You are affected if OpenClaw version is below 2026.4.24 AND the MCP loopback feature is enabled and accessible to non-owner callers.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 2026.4.24 or later

Fixed in 2026.4.24

Interim mitigation

Upgrade OpenClaw to version 2026.4.24 or later to obtain the patched code. If immediate upgrading is not feasible, disable the MCP loopback feature as a temporary workaround until the upgrade can be completed.

Recommended fix Moderate confidence

OpenClaw 2026.4.24 or later

1. Back up your current OpenClaw installation and configuration
2. Obtain OpenClaw version 2026.4.24 or later from the official GitHub repository
3. Replace the existing OpenClaw installation with the new version
4. Verify that the MCP loopback feature now properly enforces owner-only tool policies
5. Test that before-tool-call hooks are executed for all users, including loopback requests
6. Confirm the authorization bypass is no longer present

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

Fix this in Openclaw Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing4.0 h
Review / QA2.0 h

13.0 hours of engineering $2,280

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,648.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

github.comMitigationVendor Advisory
www.vulncheck.comThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-53818?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 2026.4.24 or later

Severity 6.6 Medium

Exploit likelihood EPSS, next 30 days 0.1%

Affects: Openclaw

Remediation

Need this fixed?

Fix this in Openclaw 13 hrs · Moderate

Typical engagement from $2,280

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-53818 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References