Puma's Keepalive Connections Causing Denial Of Service
Published 18 May 2021 · Updated 8 Jul 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
- <4.3.8
- Fixed in
- 4.3.8
bundle update --conservative puma # Gemfile: '>= 4.3.8'- Affected
- >=5.0.0 <5.3.1
- Fixed in
- 5.3.1
bundle update --conservative puma # Gemfile: '>= 5.3.1'Details
This vulnerability is related to CVE-2019-16770.
Impact
The fix for CVE-2019-16770 was incomplete. The original fix only protected existing connections that had already been accepted from having their requests starved by greedy persistent-connections saturating all threads in the same process. However, new connections may still be starved by greedy persistent-connections saturating all threads in all processes in the cluster.
A puma server which received more concurrent keep-alive connections than the server had threads in its threadpool would service only a subset of connections, denying service to the unserved connections.
Patches
This problem has been fixed in puma 4.3.8 and 5.3.1.
Workarounds
Setting queue_requests false also fixes the issue. This is not advised when using puma without a reverse proxy, such as nginx or apache, because you will open yourself to slow client attacks (e.g. slowloris)).
The fix is very small. A git patch is available here for those using unsupported versions of Puma.
For more information
If you have any questions or comments about this advisory:
- Open an issue in Puma.
- To report problems with this fix or to report another vulnerability, see our security policy.
Acknowledgements
Thank you to @MSP-Greg, @wjordan and @evanphx for their review on this issue.
Thank you to @ioquatix for providing a modified fork of wrk which made debugging this issue much easier.
Is GHSA-q28m-8xjw-8vr5 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
- 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
References
- Linkgithub.com/puma/puma/security/advisories/GHSA-q28m-8xjw-8vr5
- Advisorynvd.nist.gov/vuln/detail/CVE-2021-29509
- Linkgist.github.com/nateberkopec/4b3ea5676c0d70cbb37c82d54be25837
- Packagegithub.com/puma/puma
- Linkgithub.com/puma/puma/security/policy
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/puma/CVE-2021-29509.yml
- Linklists.debian.org/debian-lts-announce/2022/08/msg00015.html
- Linkrubygems.org/gems/puma
- Linksecurity.gentoo.org/glsa/202208-28
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.