Disclosed weakness · no CVE recorded

OpenClaw could interpret a scoped Gateway request differently across routing checks

OpenClaw · OpenClaw · Gateway capability routing

First documented disclosure · Review checkpoint

Summary

Different Gateway components could disagree on the destination of an ambiguous capability-scoped request.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The upstream sources document the behavior and correction. They identify no malicious use.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Policy checks and downstream routing did not share one interpretation of certain paths.

Conditions required

A request reaches the Gateway with a scoped capability and an ambiguous destination.

Potential impact

Policy enforcement could depend on which component interpreted the request.

Affected versions and configurations

The upstream report identifies the affected behavior without specifying a complete version range.

Fix and mitigation status

The 2026.11.4 stable release includes this issue-specific correction.

Practical next steps

Deploy the fix so ambiguous scoped requests are rejected.

Operating lesson

Use a single verified interpretation for both authorization and dispatch.

Evidence and limits

Upstream described inconsistent routing and reported no known exploit. Unauthorized access was not demonstrated.

Sources