Skip to content
Noroxi
OSV ecosystem advisory

GHSA-g27f-9qjv-22pm: OpenClaw log poisoning (indirect prompt injection) via WebSocket headers

LowCVSS 3.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 12/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: openclaw (npm) 2026.2.13.

Low priority for now. Upgrade to openclaw (npm) 2026.2.13 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

### 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.

Published
Feb 17, 2026
Updated
Feb 17, 2026
EPSS
—

Report tools

JSON

Action score

12

Monitor

Low priority for now.

CVSS
12 / 40 · 3.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-g27f-9qjv-22pm

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
npmopenclaw

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmopenclawbefore 2026.2.132026.2.13

Same product

npm: all records

Other highest-scoring records for the same primary product.

  • GHSA-943q-mwmv-hhvhOpenClaw: Gateway /tools/invoke tool escalation + ACP permission auto-approval
    35Monitor
  • GHSA-474h-prjg-mmw3OpenClaw: Sandboxed sessions_spawn(runtime="acp") bypassed sandbox inheritance and allowed host ACP initialization
    32Monitor
  • GHSA-56f2-hvwg-5743OpenClaw affected by SSRF in Image Tool Remote Fetch
    30Monitor

Published before and after this one in the same product

  • ← EarlierGHSA-hv93-r4j3-q65fFeb 17, 2026 · OpenClaw Hook Session Key Override Enables Targeted Cross-Session Routing
    28Monitor
  • Later →GHSA-chm2-m3w2-wcxmFeb 17, 2026 · OpenClaw Google Chat spoofing access with allowlist authorized mutable email principal despite sender-ID mismatch
    0Monitor
  • Later →GHSA-w5c7-9qqw-6645Feb 18, 2026 · OpenClaw inter-session prompts could be treated as direct user instructions
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:openclaw2026.2.13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

osv

References

All records