Is CVE-2026-62208 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-62208 being exploited in the wild.

How severe is CVE-2026-62208?

Medium severity, with a CVSS score of 6.5, published 17 July 2026.

Which products and versions are affected?

openclaw (npm) SEMVER:introduced=0,fixed=2026.6.5; Openclaw before 2026.6.5.

Is there a fix for CVE-2026-62208?

Yes. openclaw (npm): upgrade to 2026.6.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-62208 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-62208?

Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-62208: OpenClaw credential leakage via Authorization header forwarding in MCP SSE

CVE-2026-62208 · Severity: medium · CVSS 6.5 · Published 2026-07-17

OpenClaw, a tool used for managing Model Context Protocol (MCP) connections, contains a flaw where sensitive login credentials can be accidentally shared with unauthorized third-party servers. If an attacker can trigger a specific type of network redirect, they may capture the user's authorization headers, potentially allowing them to perform actions as that user. This could lead to unauthorized access to private data or services managed by the platform.

Technologies: openclaw (npm), Openclaw. Vendors: npm, Openclaw.

Quick answers

Is CVE-2026-62208 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-62208 being exploited in the wild.
How severe is CVE-2026-62208?: Medium severity, with a CVSS score of 6.5, published 17 July 2026.
Which products and versions are affected?: openclaw (npm) SEMVER:introduced=0,fixed=2026.6.5; Openclaw before 2026.6.5.
Is there a fix for CVE-2026-62208?: Yes. openclaw (npm): upgrade to 2026.6.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-62208 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-62208?: Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

openclaw (npm): upgrade to 2026.6.5 or later
```
npm install openclaw@2026.6.5
```

Technical details

A credential leakage vulnerability exists in OpenClaw versions prior to 2026.6.5 due to improper handling of HTTP redirects within the Model Context Protocol (MCP) Server-Sent Events (SSE) implementation. When a redirect occurs, the application fails to strip sensitive 'Authorization' headers before forwarding the request to the new destination. An attacker with low privileges who can influence the input path or reach the affected feature can capture these headers, leading to an exposure of sensitive information (CWE-200, CWE-522). The vulnerability is exploitable over the network without user interaction, provided the affected feature is enabled. The issue is resolved in version 2026.6.5.

Affected products

OpenClaw OpenClaw before 2026.6.5

Identifiers

CVE-2026-62208
GHSA-9c3v-684m-579c

Timeline

2026-06-30: advisory: GitHub Security Advisory published
2026-07-17: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.