DEV Community

CVE Reports
CVE Reports

Posted on • Originally published at cvereports.com

GHSA-5JVJ-HXMH-6H6J: GHSA-5JVJ-HXMH-6H6J: Authorization Bypass in OpenClaw Gateway HTTP Session History

#security #cve #cybersecurity #ghsa

GHSA-5JVJ-HXMH-6H6J: Authorization Bypass in OpenClaw Gateway HTTP Session History

Vulnerability ID: GHSA-5JVJ-HXMH-6H6J
CVSS Score: 5.3
Published: 2026-03-29

The OpenClaw Gateway HTTP API contains an incorrect authorization implementation that fails to enforce operator read scopes on the session history route. This flaw allows users with low-privileged authentication tokens to read sensitive chat transcripts that should be restricted to operators with explicit read permissions.

TL;DR

An authorization bypass in the openclaw npm package allows any user with a valid Bearer token to read session chat histories via the HTTP API, bypassing the strict operator.read scope requirements enforced on the equivalent WebSocket interface.

⚠️ Exploit Status: POC

Technical Details

  • CWE ID: CWE-863
  • Attack Vector: Network (HTTP)
  • Authentication Required: Yes (Low Privilege)
  • Impact: Confidentiality (High)
  • Exploit Status: Proof-of-Concept Available
  • CVSSv3 Score: 5.3

Affected Systems

  • OpenClaw Gateway HTTP API
  • openclaw npm package
  • openclaw: <= 2026.3.24 (Fixed in: 2026.3.25)

Code Analysis

Commit: 1c45123

Fix HTTP session history route authorization bypass

Exploit Details

  • Public Commit: The patch commit contains details and testing reproduction methods outlining the attack.

Mitigation Strategies

  • Update the openclaw package to the patched version.
  • Update HTTP API clients to send the required x-openclaw-scopes header.
  • Implement a centralized authorization middleware to prevent transport-specific access control gaps.

Remediation Steps:

  1. Identify all projects utilizing the openclaw npm package.
  2. Modify the package.json to require openclaw version 2026.3.25 or greater.
  3. Run npm install or yarn install to apply the update.
  4. Update any custom HTTP clients querying the /sessions/:sessionKey/history route to append the x-openclaw-scopes: operator.read header.
  5. Verify the fix by attempting to access the route with a token lacking the operator.read scope and confirming a 403 response.

References

Read the full report for GHSA-5JVJ-HXMH-6H6J on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)