CVE-2026-32037

In OpenClaw MSTeams media download flows, redirect handling could bypass configured mediaAllowHosts checks in specific attachment paths. Redirect chains were not consistently constrained to allowlisted targets before accepting fetched content.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected versions: <= 2026.2.21-2 (latest published at triage time)
• Fixed in: 2026.2.22 (planned next release)

Fix Commit(s)

• 73d93dee64127a26f1acd09d0403b794cdeb4f5c
• b34097f62df9d1960cc22600269cd3f3284e2124

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.22). Once that npm release is published, this advisory can be published without further version-field edits.

OpenClaw thanks @tdjackey for reporting.

Attackers able to supply or influence attachment URLs could force redirect chains to non-allowlisted targets, weakening SSRF boundary controls for MSTeams media ingestion.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-32037 has a CVSS score of 6.0 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.22); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32037? CVE-2026-32037 is a high-severity server-side request forgery (SSRF) vulnerability in openclaw (npm), affecting versions < 2026.2.22. It is fixed in 2026.2.22. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2026-32037? CVE-2026-32037 has a CVSS score of 6.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32037? openclaw (npm) versions < 2026.2.22 is affected.
4. Is there a fix for CVE-2026-32037? Yes. CVE-2026-32037 is fixed in 2026.2.22. Upgrade to this version or later.
5. Is CVE-2026-32037 exploitable, and should I be worried? Whether CVE-2026-32037 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32037 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32037? Upgrade openclaw to 2026.2.22 or later.