Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

OpenClaw: MCP Streamable HTTP redirects could forward configured custom headers to another origin

CVE-2026-53840GHSA-rjxq-qqhf-8hwh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (openclaw 2026.5.12), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm openclaw

    Affected
    < 2026.5.12
    Fixed in
    2026.5.12

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS
  • CVE-2026-53840: 0.22% estimated exploitation activity in the next 30 days; percentile 13.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary OpenClaw supports remote MCP Streamable HTTP servers with operator-configured custom headers. In affected releases, those headers could be forwarded when the MCP endpoint responded with a cross-origin redirect. This issue is limited to configured MCP Streamable HTTP servers that use custom headers. It does not expose unrelated OpenClaw credentials. Affected configurations This affects deployments where an MCP server is configured with: - transportType: "streamable-http" - sensitive custom headers under mcp.servers..headers - an MCP endpoint that is malicious, compromised, or able to redirect to another origin Impact Custom MCP headers, such as API keys or tenant-routing headers, could be sent to the redirect target. The exposed credential scope depends on the header the operator configured for that MCP server. Patched Versions The first stable patched version is 2026.5.12. Mitigations Upgrade to openclaw@2026.5.8 or later. Before upgrading, avoid custom MCP headers with…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-rjxq-qqhf-8hwh

  2. Revision 1 · created ·

    Published from osv record GHSA-rjxq-qqhf-8hwh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-53840

Advisory: OpenClaw: MCP Streamable HTTP redirects could forward configured custom headers to another origin
IDs: CVE-2026-53840, GHSA-rjxq-qqhf-8hwh
Record: https://patchnext.com/advisories/cve-2026-53840 (revision 2, source checked 26 Oct 2026, 12:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.5.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected < 2026.5.12; fixed in 2026.5.12

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rjxq-qqhf-8hwh (OSV record GHSA-rjxq-qqhf-8hwh lists affected ranges: npm openclaw >=0 <2026.5.12 (fixed))
- Verified: https://github.com/advisories/GHSA-rjxq-qqhf-8hwh (GitHub-reviewed advisory GHSA-rjxq-qqhf-8hwh lists affected ranges: npm openclaw >=0 <2026.5.12)

Commands are suggestions: review each one before running it.

Loading voting…