Skip to main content
VulnerabilityPublished Updated

CVE-2026-53832: OpenClaw · Same-host trusted-proxy deployments could accept local forged identity headers

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 2026.5.18 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.5.18
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.5.18.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.5.18
Fixed in
  • 2026.5.18

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in OpenClaw CLI version 2026.5.18. Operators should upgrade to this version to remediate the vulnerability. Additionally, bind the trusted-proxy ingress behind the actual proxy and firewall to prevent direct same-host access. Maintain narrow channel and tool allowlists, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.

Description

OpenClaw CLI versions from 2026.1.29 up to but not including 2026.5.18 have a vulnerability where same-host trusted-proxy deployments could accept locally forged identity headers. This allows a local caller on the same host who can access the proxy-facing Gateway port to supply identity headers normally reserved for the trusted proxy. The vulnerability affects operator identity handling when the feature is enabled and reachable. A patch is available in version 2026.5.18. Mitigations include restricting access to the trusted-proxy ingress behind a proxy and firewall, narrowing allowlists, avoiding sharing Gateways between untrusted users, and disabling the feature if not needed.

References

Community reviews

Loading reviews…