p PatchFirst

CVE-2026-47736

CVE-2026-47736 · Puma PROXY Protocol v1 Parser Allows Remote Memory Exhaustion

CVSS 7.5 · High · EPSS 0.3% · Fix available

Compare with your installed version

Affected products and known fixed versions are public information. Compare them with your installed version.

  • pumaNo fix published
  • puma Debian 12Update to 5.6.5-3+deb12u2
  • puma Debian 13No fix published
  • puma Debian 14Update to 8.0.2-1
  • and 6 more

Check the installed version:

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="puma"'

Assess your server’s risks

The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.

Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.

curl -fsSL https://patchfirst.dev/check.sh | sh
Check your server for free →

Channels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Puma is a Ruby/Rack web server built for parallelism. From 5.5.0 until 7.2.1 and 8.0.2, when PROXY protocol v1 support is enabled, Puma reads incoming bytes into an internal buffer while waiting for CRLF to determine whether a PROXY v1 line is present, allowing an attacker that continuously sends bytes without CRLF to cause unbounded in-process memory growth and additional CPU cost from repeatedly scanning the growing buffer. This issue is fixed in versions 7.2.1 and 8.0.2.

Published
Updated

Fixes in distributions

Stack: system · ruby

Affected products and versions

  • puma

    Versions
    • >= 5.5.0, < 7.2.1: Affected
    • >= 8.0.0, < 8.0.2: Affected

    No fix published

  • puma Debian 12

    Versions
    • 5.6.5-3
    • 5.6.5-3+deb12u1
    Affected ranges
    • ECOSYSTEM: < 5.6.5-3+deb12u2

    Update to 5.6.5-3+deb12u2

  • puma Debian 13

    Versions
    • 6.6.0-4
    • 8.0.2-1
    • 8.0.2-2
    • 8.0.2-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • puma Debian 14

    Versions
    • 6.6.0-4
    Affected ranges
    • ECOSYSTEM: < 8.0.2-1

    Update to 8.0.2-1

  • puma RubyGems

    Versions
    • 8.0.0
    • 8.0.1
    Affected ranges
    • ECOSYSTEM: ≥ 8.0.0, < 8.0.2

    Update to 8.0.2

  • puma RubyGems

    Versions
    • 5.5.0
    • 5.5.1
    • 5.5.2
    • 5.6.0
    • 5.6.1
    • 5.6.2
    All versions (37)
    • 5.6.4
    • 5.6.5
    • 5.6.6
    • 5.6.7
    • 5.6.8
    • 5.6.9
    • 6.0.0
    • 6.0.1
    • 6.0.2
    • 6.1.0
    • 6.1.1
    • 6.2.0
    • 6.2.1
    • 6.2.2
    • 6.3.0
    • 6.3.1
    • 6.4.0
    • 6.4.1
    • 6.4.2
    • 6.4.3
    • 6.5.0
    • 6.6.0
    • 6.6.1
    • 7.0.0
    • 7.0.0.pre1
    • 7.0.1
    • 7.0.2
    • 7.0.3
    • 7.0.4
    • 7.1.0
    • 7.2.0
    Affected ranges
    • ECOSYSTEM: ≥ 5.5.0, < 7.2.1

    Update to 7.2.1

  • puma Ubuntu Pro 20.04 LTS

    Versions
    • 3.12.0-2ubuntu1
    • 3.12.0-4ubuntu1
    • 3.12.4-1ubuntu2
    • 3.12.4-1ubuntu2+esm1
    • 3.12.4-1ubuntu2+esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • puma Ubuntu Pro 22.04 LTS

    Versions
    • 4.3.6-1ubuntu4
    • 5.5.2-2ubuntu2
    • 5.5.2-2ubuntu2+esm1
    • 5.5.2-2ubuntu2+esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • puma Ubuntu 24.04 LTS

    Versions
    • 5.6.5-4ubuntu2
    • 5.6.5-4ubuntu3
    • 6.4.2-4ubuntu1
    • 6.4.2-4ubuntu3
    • 6.4.2-4ubuntu4
    • 6.4.2-4ubuntu4.3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • puma Ubuntu 26.10

    Versions
    • 6.6.0-4build1
    • 8.0.2-3build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • puma Ubuntu 26.04 LTS

    Versions
    • 6.6.0-4
    • 6.6.0-4build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →