Skip to main content
VulnerabilityPublished Updated

CVE-2026-35656: OpenClaw · Forwarding header spoofing bypasses gateway.trustedProxies origin detection

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026.3.24 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.24
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 18 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.24.

Affected software

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

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 and should be applied by upgrading to openclaw CLI version 2026.3.22 or later. The fix ignores loopback forwarded hops before trusted-proxy client resolution, preventing spoofing of the client origin. Users should verify they are running a fixed version to ensure protection against this vulnerability.

Description

A vulnerability in the openclaw CLI prior to version 2026.3.22 allows spoofed loopback hops in forwarding headers to bypass the gateway.trustedProxies origin detection. This can weaken downstream authentication and rate-limiting decisions that rely on accurate client origin identification. The issue is fixed in version 2026.3.22 and later.

References

Community reviews

Loading reviews…