Skip to main content
VulnerabilityPublished Updated

CVE-2026-53840: OpenClaw · MCP Streamable HTTP redirects could forward configured custom headers to another origin

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 2026.5.12 soon.

Data as of 19 Nov 2026, 20:25 UTC

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

What to do

Upgrade openclaw-cli to 2026.5.12.

Affected software

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

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

AI-suggested

Upgrade OpenClaw CLI to version 2026.5.12 or later to apply the official fix. Before upgrading, avoid using custom MCP headers with MCP servers that are not fully trusted. Additionally, rotate any MCP-specific credentials that may have been exposed due to this vulnerability.

Description

OpenClaw CLI versions from 2026.1.29 up to but not including 2026.5.12 have a vulnerability where custom headers configured for MCP Streamable HTTP servers may be forwarded to a different origin if the MCP endpoint issues a cross-origin redirect. This can expose sensitive headers such as API keys or tenant-routing headers to unintended recipients. The issue only affects deployments using streamable-http transport with custom headers and MCP endpoints that can redirect cross-origin. A fix is available starting with version 2026.5.12.

References

Community reviews

Loading reviews…