GHSA-g27f-9qjv-22pm: Openclaw OpenClaw Log Poisoning (indirect Prompt Vulnerability

LOW
Share
CVSS 3.1
CWE-117
Published
Advisory Summary

GHSA-g27f-9qjv-22pm is a LOW (CVSS 3.1) openclaw log poisoning (indirect prompt vulnerability (CWE-117: Improper Output Neutralization for Logs) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw log poisoning (indirect prompt injection) via websocket headers. Remediation is available by upgrading affected packages to version 2026.2.13.

GHSA-g27f-9qjv-22pm at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-g27f-9qjv-22pm
Severity LOW
CVSS v3.1 Base Score 3.1
CWE Classification CWE-117: Improper Output Neutralization for Logs
Affected Product Openclaw
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 3.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix GHSA-g27f-9qjv-22pm

To remediate this vulnerability, upgrade all affected Openclaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.2.13 
npm install openclaw@2026.2.13
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-g27f-9qjv-22pm, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of Openclaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.2.13), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-117: Improper Output Neutralization for Logs, where the product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file. In Openclaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary In `openclaw` versions prior to `2026.2.13`, OpenClaw logged certain WebSocket request headers (including `Origin` and `User-Agent`) without neutralization or length limits on the "closed before connect" path. If an unauthenticated client can reach the gateway and send crafted header values, those values may be written into core logs. Under workflows where logs are later read or interpreted by an LLM (for example via AI-assisted debugging), this can increase the risk of indirect prompt injection (log poisoning). ### Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `<= 2026.2.12` - Fixed: `>= 2026.2.13` ### Details - Component: `src/gateway/server/ws-connection.ts` - Trigger: WebSocket connection closes before completing the connect/handshake; header values are included in the log message and structured context. ### Impact This issue is primarily an indirect prompt injection risk and depends on downstream log consumption behavior. If you do not feed logs into an LLM or other automation, impact is limited. ### Fix Header values written to gateway logs are now sanitized and truncated (including removal of control/format characters and length limiting). - Fix commits: `d637a263505448bf4505b85535babbfaacedbaac`, `e84318e4bcdc948d92e57fda1eb763a65e1774f0` (PR #15592) ### Workarounds - Upgrade to `openclaw@2026.2.13` or later. - Treat logs as untrusted input when using AI-assisted debugging (sanitize/escape, and do not auto-execute instructions derived from logs). - Restrict gateway network exposure; apply reverse-proxy limits on header size where applicable. Thanks @pkerkhofs for reporting.

GHSA-g27f-9qjv-22pm Affected Openclaw Versions

1 component(s)
Fixed Versions:
2026.2.13
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm/openclaw
npm
< 2026.2.13
2026.2.13

References

GitHub Advisory / Wiki ADVISORY
https://github.com/openclaw/openclaw/security/advisories/GHSA-g27f-9qjv-22pm
Openclaw Source Repository REPOSITORY
https://github.com/openclaw/openclaw/pull/15592
Security Fix Commit FIX COMMIT
https://github.com/openclaw/openclaw/commit/d637a263505448bf4505b85535babbfaacedbaac
Openclaw Source Repository REPOSITORY
https://github.com/openclaw/openclaw
Openclaw Release RELEASE
https://github.com/openclaw/openclaw/releases/tag/v2026.2.13

Frequently Asked Questions

What is GHSA-g27f-9qjv-22pm?
GHSA-g27f-9qjv-22pm is a security vulnerability in Openclaw involving OpenClaw log poisoning (indirect prompt injection) via WebSocket headers under CWE-117: Improper Output Neutralization for Logs.
Which Openclaw versions are affected?
Affected versions include releases prior to 2026.2.13 across affected packages: openclaw.
What version fixes GHSA-g27f-9qjv-22pm?
Upgrading to 2026.2.13 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.2.13. Upgrade your dependency to 2026.2.13 or later.
What is the CVSS score of GHSA-g27f-9qjv-22pm?
GHSA-g27f-9qjv-22pm has a CVSS v3.1 base score of 3.1 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N.
What CWE is associated with GHSA-g27f-9qjv-22pm?
GHSA-g27f-9qjv-22pm is classified under CWE-117: Improper Output Neutralization for Logs (The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.).
How can I check npm dependencies for GHSA-g27f-9qjv-22pm?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g27f-9qjv-22pm",
  "modified" : "2026-02-17T21:31:39Z",
  "published" : "2026-02-17T21:31:39Z",
  "aliases" : [ ],
  "summary" : "OpenClaw log poisoning (indirect prompt injection) via WebSocket headers",
  "details" : "### Summary\nIn `openclaw` versions prior to `2026.2.13`, OpenClaw logged certain WebSocket request headers (including `Origin` and `User-Agent`) without neutralization or length limits on the \"closed before connect\" path.\n\nIf an unauthenticated client can reach the gateway and send crafted header values, those values may be written into core logs. Under workflows where logs are later read or interpreted by an LLM (for example via AI-assisted debugging), this can increase the risk of indirect prompt injection (log poisoning).\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Affected: `<= 2026.2.12`\n- Fixed: `>= 2026.2.13`\n\n### Details\n- Component: `src/gateway/server/ws-connection.ts`\n- Trigger: WebSocket connection closes before completing the connect/handshake; header values are included in the log message and structured context.\n\n### Impact\nThis issue is primarily an indirect prompt injection risk and depends on downstream log consumption behavior. If you do not feed logs into an LLM or other automation, impact is limited.\n\n### Fix\nHeader values written to gateway logs are now sanitized and truncated (including removal of control/format characters and length limiting).\n- Fix commits: `d637a263505448bf4505b85535babbfaacedbaac`, `e84318e4bcdc948d92e57fda1eb763a65e1774f0` (PR #15592)\n\n### Workarounds\n- Upgrade to `openclaw@2026.2.13` or later.\n- Treat logs as untrusted input when using AI-assisted debugging (sanitize/escape, and do not auto-execute instructions derived from logs).\n- Restrict gateway network exposure; apply reverse-proxy limits on header size where applicable.\n\nThanks @pkerkhofs for reporting.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.2.13"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-g27f-9qjv-22pm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/pull/15592"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/d637a263505448bf4505b85535babbfaacedbaac"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/releases/tag/v2026.2.13"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-117" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-17T21:31:39Z",
    "nvd_published_at" : null
  }
}