GitHub Advisoryadvisory · npm

GHSA-2rgf-hm63-5qph OpenClaw improperly parses X-Forwarded-For behind trusted proxies allows client IP spoofing in security decisions

MEDIUM Published 2026-03-03 Modified 2026-03-25 Official page ↗
Aliases
CVE-2026-32029
Ecosystem
npm
Packages
openclaw
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Weaknesses
CWE-345, CWE-807
Reviewed
2026-03-03

Affected packages

• npm openclaw: < 2026.2.21 → fixed in 2026.2.21

Description

Summary OpenClaw used left-most `X-Forwarded-For` values when requests came from configured trusted proxies. In proxy chains that append/preserve header values, this could let attacker-controlled header content influence security decisions tied to client IP. Affected Packages / Versions • Package: `openclaw` (npm) • Affected: `<= 2026.2.19-2` • Patched: `2026.2.21` (planned next release) Impact Possible client-IP spoofing in security-sensitive paths (for example auth rate-limit identity and local/private classification) for deployments behind trusted proxies with non-recommended forwarding behavior. Scope Note OpenClaw docs recommend reverse proxies overwrite (not append/preserve) inbound forwarding headers. This condition reduces severity. Fix Commit(s) • `07039dc089e51589a213ec0d16f8d6f2cd871fa1` • `8877bfd11ec7760b115b2d0d7500a45da2749747` Release Process Note `patched_versions` is pre-set to the planned next release (`2026.2.21`). After npm release is out, publish this advisory. OpenClaw thanks @AnthonyDiSanti for reporting.

Related

Alias · CVE (1)

  • CVE-2026-32029 OpenClaw versions prior to 2026.2.21 improperly parse the left-most X-Forwarded-For header value when requests originate from configured… vulnerability

Weakness · CWE (2)

  • CWE-345 Insufficient Verification of Data Authenticity weakness
  • CWE-807 Reliance on Untrusted Inputs in a Security Decision weakness

References