GitHub Advisoryadvisory · npm

GHSA-844j-xrrq-wgh4 OpenClaw: Forwarding header spoofing bypasses gateway.trustedProxies origin detection

MEDIUM Published 2026-03-26 Modified 2026-04-10 Official page ↗
Aliases
CVE-2026-35656
Ecosystem
npm
Packages
openclaw
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Weaknesses
CWE-290
Reviewed
2026-03-26

Affected packages

• npm openclaw: < 2026.3.22 → fixed in 2026.3.22

Description

Summary When gateway.trustedProxies was configured, spoofed loopback hops in forwarding headers could be accepted as the client origin and weaken downstream auth and rate-limit decisions. Affected Packages / Versions • Package: `openclaw` (npm) • Affected: = 2026.3.22 • Latest released tag checked: `v2026.3.23-2` (`630f1479c44f78484dfa21bb407cbe6f171dac87`) • Latest published npm version checked: `2026.3.23-2` Fix Commit(s) • `fc2d29ea926f47c428c556e92ec981441228d2a4` Release Status The fix shipped in `v2026.3.22` and remains present in `v2026.3.23` and `v2026.3.23-2`. Code-Level Confirmation • src/gateway/net.ts now ignores loopback forwarded hops before trusted-proxy client resolution. • That shipped origin fix is the one consumed by canvas auth and gateway auth-rate-limit paths that rely on resolved client identity. OpenClaw thanks @lintsinghua for reporting.

Related

Alias · CVE (1)

  • CVE-2026-35656 OpenClaw before 2026.3.22 contains an authentication bypass vulnerability in the X-Forwarded-For header processing when trustedProxies is… vulnerability

Weakness · CWE (1)

  • CWE-290 Authentication Bypass by Spoofing weakness

References