openclaw
Affected
- introduced
0, fixed2026.2.13(semver)
Fixed versions
2026.2.13
Fix
- Fixed version
2026.2.13npm install [email protected]
Advisory
Also known as: None
OpenClaw log poisoning (indirect prompt injection) via WebSocket headers
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
openclaw (npm)<= 2026.2.12>= 2026.2.13Details
src/gateway/server/ws-connection.tsImpact
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).
d637a263505448bf4505b85535babbfaacedbaac, e84318e4bcdc948d92e57fda1eb763a65e1774f0 (PR #15592)Workarounds
[email protected] or later.Thanks @pkerkhofs for reporting.
Low Basis: The source's own band: LOW
0, fixed 2026.2.13 (semver)2026.2.13
2026.2.13npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0