Puma used with Rails may lead to Information Exposure
Published 11 Feb 2022 · Updated 4 Feb 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
- >=5.0.0 <5.6.2
- Fixed in
- 5.6.2
bundle update --conservative puma # Gemfile: '>= 5.6.2'- Affected
- <4.3.11
- Fixed in
- 4.3.11
bundle update --conservative puma # Gemfile: '>= 4.3.11'Details
Impact
Prior to puma version 5.6.2, puma may not always call close on the response body. Rails, prior to version 7.0.2.2, depended on the response body being closed in order for its CurrentAttributes implementation to work correctly.
From Rails:
> Under certain circumstances response bodies will not be closed, for example a bug in a webserver[1] or a bug in a Rack middleware. In the event a response is not notified of a close, ActionDispatch::Executor will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with ActiveSupport::CurrentAttributes.
The combination of these two behaviors (Puma not closing the body + Rails' Executor implementation) causes information leakage.
Patches
This problem is fixed in Puma versions 5.6.2 and 4.3.11.
This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
See: https://github.com/advisories/GHSA-wh98-p28r-vrc9 for details about the rails vulnerability
Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.
Workarounds
Upgrade to Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
The Rails CVE includes a middleware that can be used instead.
References
- Rails CVE: CVE-2022-23633
For more information
If you have any questions or comments about this advisory:
- Open an issue in puma
- See our security policy
Is GHSA-rmj8-8hhh-gv5h 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-rmj8-8hhh-gv5h
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-23634
- Linkgithub.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb
- Advisorygithub.com/advisories/GHSA-rmj8-8hhh-gv5h
- Advisorygithub.com/advisories/GHSA-wh98-p28r-vrc9
- Packagegithub.com/puma/puma
- Linkgithub.com/rubysec/ruby-advisory-db/blob/master/gems/puma/CVE-2022-23634.yml
- Linkgroups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1
- Linklists.debian.org/debian-lts-announce/2022/05/msg00034.html
- Linklists.debian.org/debian-lts-announce/2022/08/msg00015.html
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F6YWGIIKL7KKTS3ZOAYMYPC7D6WQ5OA5
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/L7NESIBFCNSR3XH7LXDPKVMSUBNUB43G
- Linklists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TUBFJ44NCKJ34LECZRAP4N5VL6USJSIB
- Linksecurity.gentoo.org/glsa/202208-28
- Linkwww.debian.org/security/2022/dsa-5146
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.