# CVE-2026-26322: OpenClaw Gateway tool allowed unrestricted gatewayUrl override > Attackers with tool invocation privileges can force the OpenClaw host to connect to arbitrary internal or external URLs, enabling network probing and potential data access. - **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Feb 2026 - **Updated:** 20 Feb 2026 - **Also known as:** GHSA-g6q9-8fvw-f7rf ## What is CVE-2026-26322? CVE-2026-26322 is a high-severity server-side request forgery vulnerability in Openclaw Openclaw, published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description OpenClaw is a personal AI assistant. Prior to OpenClaw version 2026.2.14, the Gateway tool accepted a tool-supplied `gatewayUrl` without sufficient restrictions, which could cause the OpenClaw host to attempt outbound WebSocket connections to user-specified targets. This requires the ability to invoke tools that accept `gatewayUrl` overrides (directly or indirectly). In typical setups this is limited to authenticated operators, trusted automation, or environments where tool calls are exposed to non-operators. In other words, this is not a drive-by issue for arbitrary internet users unless a deployment explicitly allows untrusted users to trigger these tool calls. Some tool call paths allowed `gatewayUrl` overrides to flow into the Gateway WebSocket client without validation or allowlisting. This meant the host could be instructed to attempt connections to non-gateway endpoints (for example, localhost services, private network addresses, or cloud metadata IPs). In the common case, this results in an outbound connection attempt from the OpenClaw host (and corresponding errors/timeouts). In environments where the tool caller can observe the results, this can also be used for limited network reachability probing. If the target speaks WebSocket and is reachable, further interaction may be possible. Starting in version 2026.2.14, tool-supplied `gatewayUrl` overrides are restricted to loopback (on the configured gateway port) or the configured `gateway.remote.url`. Disallowed protocols, credentials, query/hash, and non-root paths are rejected. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-26322? 2 open source packages ship an affected version, including openclaw. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `openclaw` | npm | All versions | 2026.2.14 | | `openclaw` | npm | All versions | 2026.2.14 | Products: Openclaw Openclaw. ## How do I fix CVE-2026-26322? Upgrade openclaw to 2026.2.14 or later. ## Is CVE-2026-26322 being exploited? There is no known exploitation of CVE-2026-26322 in the wild and no public exploit code. ## Other vulnerabilities in Openclaw Openclaw - [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9) - [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8) - [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4) - [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4) - [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-26322 and fix it if it is affected. What it is: CVE-2026-26322 is a high-severity server-side request forgery vulnerability in Openclaw Openclaw, published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-26322 in the wild and no public exploit code. Affected packages and fixed versions: - openclaw (npm): affected all versions; fixed in 2026.2.14 - openclaw (npm): affected all versions; fixed in 2026.2.14 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-26322/ (Markdown: https://insights.sbomify.com/CVE-2026-26322/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26322 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26322 - OSV: https://osv.dev/vulnerability/CVE-2026-26322 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-26322/ Summaries are generated and may contain mistakes; the official description above is the record.