HighGHSA-2vqw-3mp8-cgmxCVE-2026-47737

Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections

Published 9 Jun 2026 · Updated 2 Nov 2026

Is your project on an affected puma?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

pumaRubyGems
Affected
>=8.0.0 <8.0.2
Fixed in
8.0.2
Update to the fixed version for your release line, for example:bundle update --conservative puma # Gemfile: '>= 8.0.2'
pumaRubyGems
Affected
>=5.5.0 <7.2.1
Fixed in
7.2.1
Update to the fixed version for your release line, for example:bundle update --conservative puma # Gemfile: '>= 7.2.1'

Details

Impact

Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used.

PROXY protocol v1 is a connection-level protocol. Support was added to Puma in v5.5.0. A proxy sends one PROXY header at the beginning of a TCP connection, before any HTTP data. Puma incorrectly re-parsed PROXY protocol headers after each keep-alive request on the same connection. An attacker able to send HTTP requests through a trusted proxy could therefore inject a second PROXY header between HTTP requests. Puma would treat the injected header as authoritative for the next request and overwrite REMOTE_ADDR.

This can mislead applications or middleware that use REMOTE_ADDR for security decisions, rate limiting, auditing, or allow/deny lists.

Only deployments that explicitly enable PROXY protocol v1 are affected, and will have set:

set_remote_address proxy_protocol: :v1

Puma's default configuration is not affected. Deployments that do not use persistent connections to Puma are also not expected to be affected by this issue.

Patches

Users should upgrade to versions 7.2.1 or 8.0.2.

Workarounds

Disable PROXY protocol v1 parsing if it is not required:

   # remove/comment this:
   # set_remote_address proxy_protocol: :v1

Users can also disable persistent connections to Puma, for example:

enable_keep_alives false

References

Is GHSA-2vqw-3mp8-cgmx in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected puma, and gives you the command that fixes it.

More advisories for puma

  • HighCVE-2026-47736Puma PROXY Protocol v1 Parser Allows Remote Memory Exhaustion · 8 Jun 2026
  • MediumCVE-2024-45614Puma's header normalization allows for client to clobber proxy set headers · 20 Sept 2024
  • MediumCVE-2024-21647Puma HTTP Request/Response Smuggling vulnerability · 8 Jan 2024
  • CriticalCVE-2023-40175Puma HTTP Request/Response Smuggling vulnerability · 18 Aug 2023
  • CriticalCVE-2022-24790Puma vulnerable to HTTP Request Smuggling · 30 Mar 2022
  • HighCVE-2022-23634Puma used with Rails may lead to Information Exposure · 11 Feb 2022
All 14 advisories for puma

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.