Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-g27f-9qjv-22pm

LowCVSS 3.1 / 10
Published Feb 17, 2026·Last modified Feb 17, 2026
Affected Components(0)

No affected components available

Description

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.

Risk Scores
Base Score
3.1

The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a low impact on the integrity of the data.

Threat Intelligence
2.9

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Low severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard