OpenClaw Vulnerability: Local Forged Identity Headers in Trusted Proxy Deployments
Summary
GHSA-rggc-m335-3wvj: OpenClaw: Same-host trusted-proxy deployments could accept local forged identity headers. Affects openclaw versions < 2026.5.18. Fixed in 2026.5.18. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
OpenClaw is an open-source software package designed for managing and deploying applications with a focus on security and user authentication. It utilizes a trusted-operator model where authenticated operators and plugins are considered secure. However, a vulnerability has been identified in its trusted-proxy feature, allowing local callers to forge identity headers, potentially compromising the integrity of the application.
Vulnerability Detail
The vulnerability arises from the ability of a local same-host caller to reach the proxy-facing Gateway port and supply identity headers that are typically reserved for trusted proxies. This could lead to unauthorized access, as the system may accept operator identities associated with these forged headers. The impact of this vulnerability is contingent upon the operator's configuration and the extent to which lower-trust inputs can access the affected path. The CVSS score for this vulnerability is 7.7, indicating a high severity level.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2026.5.18
This is the first release that contains the fix.
npm install openclaw@2026.5.18Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, bind the trusted-proxy ingress behind the actual proxy and firewall to restrict direct same-host access. Additionally, for general hardening, maintain narrow channel and tool allowlists, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.
Conclusion
The OpenClaw vulnerability concerning local forged identity headers poses a significant risk to applications using the trusted-proxy feature. It is crucial to update to the patched version 2026.5.18 and implement recommended workarounds to mitigate potential threats. Regular monitoring and vulnerability assessments, such as those provided by Vulert, can help maintain application security.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability allows local callers to forge identity headers that can be accepted by the trusted proxy, potentially leading to unauthorized access.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
If exploited, this vulnerability could allow unauthorized users to impersonate trusted operators, leading to data breaches or unauthorized actions within the application.
Yes, the first stable patched version is 2026.5.18. Updating to this version will resolve the vulnerability.
Implement the suggested workarounds, such as binding the trusted-proxy ingress behind the actual proxy and firewall, and disabling the affected feature if it is not needed.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
