CVE-2026-62208

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-17. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OpenClaw before 2026.6.5 could forward Authorization headers during MCP SSE redirects. When the affected feature is enabled and reachable, a lower-trust caller or configured input path could execute or persist actions beyond the caller's intended authorization. Impact depends on the operator's configuration and whether lower-trust input can reach the affected path.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
17.3%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 20, 2026

Advisory Details (2)

Auto-updated Jul 17, 2026
Patch available. Sources: github.
generic

OpenClaw < 2026.6.5 Authorization Header Forwarding via SSE | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-authorization-header-forwarding-via-sse
github Patch Available

MCP SSE redirects could forward Authorization headers · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-9c3v-684m-579c

Vendor Advisories for CVE-2026-62208(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
openclaw—2026.6.5—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:21 UTCEG score recompute
  4. 2026-07-23 00:22 UTCEG score recompute
  5. 2026-07-23 00:22 UTCGHSA enrichment
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:25 UTCEPSS rescore
  9. 2026-07-21 15:25 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-19 01:56 UTCEG score recompute
  14. 2026-07-19 01:55 UTCGHSA enrichment
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-17 12:02 UTCEG score recompute
  17. 2026-07-17 12:02 UTCGHSA enrichment
  18. 2026-07-17 11:02 UTCEG score recompute
  19. 2026-07-17 11:02 UTCGHSA enrichment
  20. 2026-07-17 06:55 UTCGHSA enrichment
  21. 2026-07-17 00:26 UTCEG score recompute
  22. 2026-07-17 00:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62208?
CVE-2026-62208 is a medium vulnerability published on July 17, 2026. OpenClaw before 2026.6.5 could forward Authorization headers during MCP SSE redirects. When the affected feature is enabled and reachable, a lower-trust caller or configured input path could execute or persist actions beyond the caller's intended authorization. Impact depends on the operator's…
When was CVE-2026-62208 disclosed?
CVE-2026-62208 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62208 actively exploited?
CVE-2026-62208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-62208?
CVE-2026-62208 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-62208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62208, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62208

Explore →

Is Your Infrastructure Affected by CVE-2026-62208?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs