N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

GHSA-mhr7-2xmv-4c4q

GHSA-mhr7-2xmv-4c4q: OpenClaw: HTTP operator endpoints lack browser-origin validation in trusted-proxy mode

Summary

HTTP operator endpoints lack browser-origin validation in trusted-proxy mode

Current Maintainer Triage

Status: narrow
Normalized severity: medium
Assessment: This is a real trusted-proxy HTTP CSRF or browser-origin gap in released tags, but it is not critical because it depends on identity-bearing trusted-proxy browser deployments rather than the shared-secret HTTP operator model.

Affected Packages / Versions

Package: openclaw (npm)
Latest published npm version: 2026.3.31
Vulnerable version range: <=2026.3.28
Patched versions: >= 2026.3.31
First stable tag containing the fix: v2026.3.31

Fix Commit(s)

6b3f99a11f4d070fa5ed2533abbb3d7329ea4f0d — 2026-03-31T19:49:26+09:00

OpenClaw thanks @AntAISecurityLab for reporting.

(GitHub Advisory)

Miggo Vulnerability Database

→

GHSA-mhr7-2xmv-4c4q

GHSA-mhr7-2xmv-4c4q:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	<= 2026.3.28	2026.3.31

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability, identified as GHSA-mhr7-2xmv-4c4q, is a Cross-Site Request Forgery (CSRF) issue in OpenClaw's HTTP operator endpoints when running in trusted-proxy mode. The root cause was the lack of validation for the Origin header in incoming HTTP requests from browsers.

The analysis of the patch commit 6b3f99a11f4d070fa5ed2533abbb3d7329ea4f0d reveals that the core of the vulnerability was in the authorizeGatewayConnect function within src/gateway/auth.ts. This function handled authentication logic but, prior to the patch, did not perform any origin checks for requests authenticated via a trusted proxy. This allowed a malicious website to forge requests on behalf of an authenticated user.

The patch introduces a new function, authorizeTrustedProxyBrowserOrigin, which is now called from within authorizeGatewayConnect to validate the request's origin against a list of allowed origins.

Additionally, several higher-level functions that orchestrate HTTP request authorization were updated to propagate the necessary origin information down to authorizeGatewayConnect. These functions, authorizeGatewayHttpRequestOrReply and authorizeGatewayBearerRequestOrReply, are also identified as vulnerable because their previous implementation facilitated the bypass of origin checks. During a profiling session of an exploit, these functions would likely appear in the stack trace leading to the vulnerable code path.

Vulnerable functions

authorizeGatewayConnect

src/gateway/auth.ts

This function is responsible for authorizing gateway connections. The vulnerability lies in the fact that for trusted-proxy authentication, it previously did not validate the browser's 'Origin' header for HTTP requests. An attacker could abuse this to perform CSRF attacks. The patch adds a call to `authorizeTrustedProxyBrowserOrigin` to perform this missing validation.

authorizeGatewayHttpRequestOrReply

src/gateway/http-utils.ts

This function acts as a wrapper around `authorizeGatewayConnect` for handling HTTP requests. It was vulnerable because it did not resolve and pass the browser origin information down to `authorizeGatewayConnect`, thereby bypassing the origin check. The patch adds the `browserOriginPolicy` parameter to the call.

authorizeGatewayBearerRequestOrReply

src/gateway/http-auth-helpers.ts

Similar to `authorizeGatewayHttpRequestOrReply`, this function prepares and calls `authorizeGatewayConnect`. It was vulnerable as it failed to provide the necessary browser origin policy, leading to a lack of CSRF protection for bearer token requests in a trusted-proxy setup. The fix involves passing the `browserOriginPolicy` to the authorization function.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.