puma vulnerabilities
Puma is a simple, fast, multi-threaded, and highly parallel HTTP 1.1 server for Ruby/Rack applications. Puma is intended for use in both development and production environments. It's great for highly parallel Ruby implementations such as JRuby and TruffleRuby as well as as providing process worker support to support CRuby well.
- Registry
- RubyGems
- Latest
- 8.1.2
- License
- BSD-3-Clause
14 known advisories
The latest version, 8.1.2, is not affected by any of them. Projects on older versions may be.
bundle update --conservative puma # Gemfile: '>= 8.1.2'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
Security advisories for puma
Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections
- Affected
- >=8.0.0 <8.0.2 · >=5.5.0 <7.2.1
- Fixed in
- 7.2.1, 8.0.2
Puma PROXY Protocol v1 Parser Allows Remote Memory Exhaustion
- Affected
- >=8.0.0 <8.0.2 · >=5.5.0 <7.2.1
- Fixed in
- 7.2.1, 8.0.2
Puma's header normalization allows for client to clobber proxy set headers
- Affected
- <5.6.9 · >=6.0.0 <6.4.3
- Fixed in
- 5.6.9, 6.4.3
Puma HTTP Request/Response Smuggling vulnerability
- Affected
- >=6.0.0 <6.4.2 · <5.6.8
- Fixed in
- 5.6.8, 6.4.2
Puma HTTP Request/Response Smuggling vulnerability
- Affected
- <5.6.7 · >=6.0.0 <6.3.1
- Fixed in
- 5.6.7, 6.3.1
Puma vulnerable to HTTP Request Smuggling
- Affected
- >=5.0.0 <5.6.4 · <4.3.12
- Fixed in
- 4.3.12, 5.6.4
Puma used with Rails may lead to Information Exposure
- Affected
- >=5.0.0 <5.6.2 · <4.3.11
- Fixed in
- 4.3.11, 5.6.2
Puma with proxy which forwards LF characters as line endings could allow HTTP request smuggling
- Affected
- >=5.0.0 <5.5.1 · <4.3.9
- Fixed in
- 4.3.9, 5.5.1
Puma's Keepalive Connections Causing Denial Of Service
- Affected
- <4.3.8 · >=5.0.0 <5.3.1
- Fixed in
- 4.3.8, 5.3.1
HTTP Smuggling via Transfer-Encoding Header in Puma
- Affected
- <3.12.6 · >=4.0.0 <4.3.5
- Fixed in
- 3.12.6, 4.3.5
HTTP Smuggling via Transfer-Encoding Header in Puma
- Affected
- <3.12.5 · >=4.0.0 <4.3.4
- Fixed in
- 3.12.5, 4.3.4
HTTP Response Splitting (Early Hints) in Puma
- Affected
- <3.12.4 · >=4.0.0 <4.3.3
- Fixed in
- 3.12.4, 4.3.3
HTTP Response Splitting in Puma
- Affected
- <3.12.4 · >=4.0.0 <4.3.3
- Fixed in
- 3.12.4, 4.3.3
A poorly-behaved client could use keepalive requests to monopolize Puma's reactor and create a denial of service attack
- Affected
- <3.12.2 · >=4.0.0 <4.3.1
- Fixed in
- 3.12.2, 4.3.1
Is your puma version vulnerable?
- puma 8.1No known advisories in 8.1.2
- puma 8.0No known advisories in 8.0.4
- puma 7.2No known advisories in 7.2.3
- puma 7.12 advisories in 7.1.0
- puma 7.02 advisories in 7.0.4
- puma 6.62 advisories in 6.6.1
- puma 6.52 advisories in 6.5.0
- puma 6.42 advisories in 6.4.3
- puma 6.34 advisories in 6.3.1
- puma 6.25 advisories in 6.2.2
- puma 6.15 advisories in 6.1.1
Which of your client projects still run an old puma?
NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other RubyGems packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.