---
id: "CVE-2026-119711"
kind: "vulnerability"
aliases: ["CVE-2026-119711"]
title: "PipesHub: spoofed forwarding headers bypass per-IP rate limits on login"
severity: "medium"
cvss: 6.9
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["authentication", "other", "pipeshub", "self-hosted"]
not_affected_if: ["version-0.10.0-or-later"]
published_at: "2026-10-30T16:17:54+00:00"
first_seen_at: "2026-10-30T16:31:26+00:00"
updated_at: "2026-10-30T16:32:11+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119711", "first_seen_at": "2026-10-30T16:31:26+00:00"}]
---

# PipesHub: spoofed forwarding headers bypass per-IP rate limits on login

PipesHub before 0.10.0 trusts client-supplied X-Forwarded-For or X-Real-IP headers when deciding the client IP for rate limiting. An unauthenticated attacker can rotate those header values to get fresh rate-limit buckets, enabling password spraying and flooding of OTP or password-reset emails.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the PipesHub version: `0.10.0` or later is not affected by this flaw; anything earlier is.
- Look at whether PipesHub sits behind a proxy that sets X-Forwarded-For, and whether rate limits key on the client IP that getClientIp() returns.

## Fix

- PipesHub: move to `0.10.0` or later.

## Timeline

- 2026-10-30T16:31:26+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119711

## From the sources

PipesHub before 0.10.0 contains a rate limit bypass vulnerability in getClientIp() that allows unauthenticated attackers to evade per-IP throttling by spoofing X-Forwarded-For or X-Real-IP headers. Attackers can rotate header values to obtain fresh rate-limit buckets on authentication endpoints, enabling password spraying and OTP or password-reset email flooding.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_