Puma PROXY Protocol v1 Parser Allows Remote Memory Exhaustion
Published 8 Jun 2026 · Updated 2 Nov 2026
Is your project on an affected puma?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=8.0.0 <8.0.2
- Fixed in
- 8.0.2
bundle update --conservative puma # Gemfile: '>= 8.0.2'- Affected
- >=5.5.0 <7.2.1
- Fixed in
- 7.2.1
bundle update --conservative puma # Gemfile: '>= 7.2.1'Details
Impact
PROXY protocol support for Puma was added in version 5.5.0.
When PROXY protocol v1 support is enabled, Puma reads incoming bytes into an internal buffer. It waits for "\r\n" to determine whether a PROXY v1 line is present. If an attacker opens a TCP connection and continuously sends bytes without CRLF, Puma keeps appending to this pre-parse buffer.
This can cause unbounded in-process memory growth and additional CPU cost from repeatedly scanning the growing buffer for CRLF. A single, unauthenticated TCP connection can drive significant memory growth and may cause process/container OOM or degraded availability.
Only Puma servers using the following non-default config are affected:
set_remote_address proxy_protocol: :v1
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
- Restrict direct network access to Puma listeners using PROXY protocol:
- Only allow trusted load balancers/reverse proxies to connect.
- Block arbitrary client TCP access with firewall/security group rules.
Resources
Is GHSA-qpgp-93vx-g8v8 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-47737Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections · 9 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
References
- Linkgithub.com/puma/puma/security/advisories/GHSA-qpgp-93vx-g8v8
- Linkgithub.com/puma/puma/commit/439c6136d9c2275721b7864db3ee78af7c80889f
- Linkgithub.com/puma/puma/commit/ebe9db3929ab8299d19c8f5b41e8ef4f4b22fa58
- Packagegithub.com/puma/puma
- Linkgithub.com/puma/puma/releases/tag/v7.2.1
- Linkgithub.com/puma/puma/releases/tag/v8.0.2
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/puma/CVE-2026-47736.yml
- Advisorynvd.nist.gov/vuln/detail/cve-2026-47736
- Linkwww.cve.org/CVERecord?id=CVE-2026-47736
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.