dbcve.org
OpenclawApplication

CVE-2026-32031

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-19
Fix available
A fix is available. Upgrade to 2026.2.26 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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 prior to 2026.2.26 server-http contains an authentication bypass vulnerability in gateway authentication for plugin channel endpoints due to path canonicalization mismatch between the gateway guard and plugin handler routing. Attackers can bypass authentication by sending requests with alternative path encodings to access protected plugin channel APIs without proper gateway authentication.

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 server-http versions prior to 2026.2.26 contain an authentication bypass vulnerability where path canonicalization mismatch between the gateway guard and plugin handler routing allows attackers to bypass authentication by sending requests with alternative path encodings to access protected plugin channel APIs without proper gateway authentication.

MitigationUpgrade to OpenClaw version 2026.2.26 or later, which presumably implements consistent path canonicalization in the gateway authentication layer to prevent bypass via alternative path encodings.

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.26

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify OpenClaw server-http version
    Locate the OpenClaw server-http installation and retrieve its version metadata (e.g., via CLI version flag, package manager, or version file in the installation directory). Compare the installed version against the affected range: versions prior to 2026.2.26.
    Affected if The installed version is lower than 2026.2.26.
  2. Verify gateway guard authentication configuration
    Examine the gateway guard configuration files for the server-http component. Identify whether authentication enforcement is enabled for plugin channel API routes.
    Affected if Gateway authentication is configured but relies on path matching that may not normalize alternative encodings.
  3. Test plugin channel API accessibility with path encoding variations
    Send authenticated and unauthenticated HTTP requests to a known protected plugin channel API endpoint using different path encodings (e.g., /./, /..%2F, double slashes). Compare responses with the baseline canonical path.
    Affected if Alternative path encodings return successful responses while the canonical path returns 401/403 without valid authentication.
  4. Inspect path canonicalization handling in routing layer
    Review server-http routing logs or configuration to determine how path normalization is performed before authentication decisions. Look for evidence of inconsistent handling between gateway and plugin handler.
    Affected if The routing layer does not apply consistent path canonicalization before gateway authentication checks.

A user is affected if the installed OpenClaw server-http version is prior to 2026.2.26 AND gateway authentication can be bypassed using alternative path encodings to access protected plugin channel APIs.

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.2.26 or later
Fixed in 2026.2.26
Interim mitigation

Upgrade to OpenClaw version 2026.2.26 or later, which presumably implements consistent path canonicalization in the gateway authentication layer to prevent bypass via alternative path encodings.

Recommended fix Moderate confidence

Openclaw 2026.2.26

  1. 1. Back up the current Openclaw installation and configuration data
  2. 2. Obtain the Openclaw 2026.2.26 release from the official GitHub repository or release distribution channel
  3. 3. Stop the Openclaw service to prevent active connections during upgrade
  4. 4. Install version 2026.2.26, replacing the previous installation
  5. 5. Verify the installation was successful by checking the version number
  6. 6. Start the Openclaw service
  7. 7. Test that the plugin channel endpoints now properly validate authentication through the gateway
  8. 8. Monitor logs for any authentication-related errors or anomalies

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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