Upgrade puma 3.12.6 -> 8.0.2 (security: clears 7+ CVEs)#84
Merged
Conversation
puma was pinned ~> 3.7 (3.12.6, EOL, 2020) with a stack of advisories including a Critical HTTP request-smuggling CVE; the pin blocked every fix. Bumped to ~> 8.0. Went to puma 8 rather than 6: puma 6.x still carries two open High PROXY Protocol v1 advisories (CVE-2026-47736/47737) whose only fix is ~> 7.2.1 / >= 8.0.2, so 6.x would not have fully cleared bundle-audit. puma 8.0.2 is clean. config/puma.rb and the Procfile needed no changes (standard threads/port/ environment DSL + tmp_restart plugin, all still valid in puma 8). Used --conservative so rack stays at 2.x. Both lockfiles updated. Verified locally: bundle-audit shows no remaining puma advisories; puma 8.0.2 boots as a server and serves HTTP 200 on /; app boots; test suite green (16 runs, 52 assertions, 0 failures); rubocop + reek clean.
JuanVqz
force-pushed
the
security/upgrade-puma
branch
from
July 9, 2026 05:10
f896017 to
dd9c090
Compare
JuanVqz
marked this pull request as ready for review
July 9, 2026 05:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Security upgrade:
puma~> 3.7(3.12.6) →~> 8.0(8.0.2).Why
puma was pinned at 3.12.6 — EOL (2020) and carrying a stack of advisories, including a Critical HTTP request-smuggling CVE plus several High/Medium ones. The
~> 3.7pin blocked every fix, so this is the highest-priority security item in the audit.Why puma 8 and not 6: puma 6.x still carries two open High advisories — CVE-2026-47736 / CVE-2026-47737 (PROXY Protocol v1) — whose only fix is
~> 7.2.1/>= 8.0.2. Bumping to 6.x would clear the old CVEs but leave those two. puma 8.0.2 clears all of them;bundle-auditshows no remaining puma advisories.Changes
Gemfile:gem "puma", "~> 3.7"→"~> 8.0"(resolves to 8.0.2)Gemfile.lockand the dual-bootGemfile.next.lockupdatedconfig/puma.rbuses only the standardthreads/port/environmentDSL + thetmp_restartplugin, all still valid in puma 8; theProcfile's-t/-p/-eflags are unchanged--conservativesorackstays at 2.2.23 (no collateral major)Verification (local)
bundle-audit: no remaining puma advisories (the whole point)/Rails.env)rubocopclean (exact CI config),reekcleanNote
Two non-puma advisories remain in the audit and are handled separately:
concurrent-ruby(next PR — unpin< 1.3.5, update to>= 1.3.7) andwebrick(transitive, no upstream patch yet; low exposure since puma serves in production).