OpenClaw is a personal AI assistant. Prior to 2026.2.14, browser-facing localhost mutation routes accepted cross-origin browser requests without explicit Origin/Referer validation. Loopback binding reduces remote exposure but does not prevent browser-initiated requests from malicious origins. A malicious website can trigger unauthorized state changes against a victim's local OpenClaw browser control plane (for example opening tabs, starting/stopping the browser, mutating storage/cookies) if the browser control service is reachable on loopback in the victim's browser context. Starting in version 2026.2.14, mutating HTTP methods (POST/PUT/PATCH/DELETE) are rejected when the request indicates a non-loopback Origin/Referer (or `Sec-Fetch-Site: cross-site`). Other mitigations include enabling browser control auth (token/password) and avoid running with auth disabled.

OpenClaw Multiple Vulnerabilities February 20

The version of the OpenClaw AI assistant installed on the remote host is prior to 2026.2.14. It is, therefore, affected by multiple vulnerabilities, including:

  - A command injection in the maintainer clawtributors updater script allowed arbitrary command execution via crafted     git commit author metadata. (CVE-2026-26323)

  - The Gateway tool accepted a tool-supplied gatewayUrl without sufficient restrictions, enabling SSRF via outbound     WebSocket connections to user-specified targets. (CVE-2026-26322)

  - The optional Telnyx webhook handler could accept unsigned inbound webhook requests when telnyx.publicKey is not     configured, allowing unauthenticated callers to forge Telnyx events. (CVE-2026-26319)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - OpenClaw is a personal AI assistant. Prior to 2026.2.14, browser-facing localhost mutation routes accepted
    cross-origin browser requests without explicit Origin/Referer validation. Loopback binding reduces remote
    exposure but does not prevent browser-initiated requests from malicious origins. A malicious website can
    trigger unauthorized state changes against a victim's local OpenClaw browser control plane (for example
    opening tabs, starting/stopping the browser, mutating storage/cookies) if the browser control service is
    reachable on loopback in the victim's browser context. Starting in version 2026.2.14, mutating HTTP
    methods (POST/PUT/PATCH/DELETE) are rejected when the request indicates a non-loopback Origin/Referer (or
    `Sec-Fetch-Site: cross-site`). Other mitigations include enabling browser control auth (token/password)
    and avoid running with auth disabled. (CVE-2026-26317)

ID	Name	Product	Family	Severity
299797	OpenClaw < 2026.2.14 Multiple Vulnerabilities	Nessus	Artificial Intelligence	high
437795	SCA: security update for openclaw (GHSA-3fqr-4cg8-h96q)	Tenable Cloud Security	SCA Checks	high
437795	SCA: security update for openclaw (GHSA-3fqr-4cg8-h96q)	Tenable Self-Hosted Container Security	SCA Checks	high

Detections

Analytics

CVE-2026-26317

high

Tenable Plugins

Coming Soon

high

high

high