Skip to content

Instantly share code, notes, and snippets.

@alon710
Created March 14, 2026 11:10
Show Gist options
  • Select an option

  • Save alon710/fec06abe0c60c3d8e76294f40a120083 to your computer and use it in GitHub Desktop.

Select an option

Save alon710/fec06abe0c60c3d8e76294f40a120083 to your computer and use it in GitHub Desktop.
GHSA-VMHQ-CQM9-6P7Q: GHSA-VMHQ-CQM9-6P7Q: Privilege Escalation via Incorrect Authorization in OpenClaw Gateway - CVE Security Report

GHSA-VMHQ-CQM9-6P7Q: GHSA-VMHQ-CQM9-6P7Q: Privilege Escalation via Incorrect Authorization in OpenClaw Gateway

CVSS Score: 7.1 Published: 2026-03-13 Full Report: https://cvereports.com/reports/GHSA-VMHQ-CQM9-6P7Q

Summary

A high-severity authorization bypass vulnerability exists in the OpenClaw AI assistant platform. It permits users with write-scoped permissions to interact with restricted administrative endpoints. This flaw enables attackers to modify or delete persistent browser profiles, hijacking browser infrastructure via malicious Chrome DevTools Protocol (CDP) URLs.

TL;DR

OpenClaw prior to version 2026.3.11 fails to restrict access to internal browser profile management routes. Authenticated users with operator.write scope can create or delete persistent browser profiles, enabling infrastructure hijacking.

Exploit Status: POC

Technical Details

  • CWE ID: CWE-863
  • Attack Vector: Network
  • CVSS Base Score: 7.1
  • Privileges Required: Low (operator.write)
  • Integrity Impact: High
  • Exploit Status: Proof of Concept

Affected Systems

  • OpenClaw
  • OpenClaw: < 2026.3.11 (Fixed in: 2026.3.11)

Mitigation

  • Upgrade OpenClaw deployment to version 2026.3.11 or higher.
  • Audit existing persistent browser profiles for unauthorized CDP URLs.
  • Implement principle of least privilege for operator and subagent accounts.

Remediation Steps:

  1. Verify the currently installed version of the OpenClaw package.
  2. Pull the latest container image or update the npm package to 2026.3.11.
  3. Restart the OpenClaw gateway service.
  4. Review the internal registry logs for any historical anomalous requests to /profiles/create or /profiles/:name.

References


Generated by CVEReports - Automated Vulnerability Intelligence

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment