Skip to main content
VulnerabilityPublished Updated

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

Affects pumaSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 8.0.2 soon.

Data as of 2 Nov 2026, 23:14 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 8.0.2, 7.2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade puma to 8.0.2; puma to 7.2.1.

Affected software

ProductAffectedFixed in
RubyGemspumaAffected
  • >=8.0.0 <8.0.2
Fixed in
  • 8.0.2
RubyGemspumaAffected
  • >=5.5.0 <7.2.1
Fixed in
  • 7.2.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Puma to version 7.2.1 or 8.0.2 or later, where this issue is fixed. If upgrading is not immediately possible, disable PROXY protocol v1 parsing by removing or commenting out the 'set_remote_address proxy_protocol: :v1' configuration. Additionally, restrict network access to Puma listeners that use PROXY protocol to trusted load balancers or reverse proxies only, and block arbitrary client TCP access using firewall or security group rules.

Description

Puma versions 5.5.0 through before 7.2.1 and 8.0.0 through before 8.0.2 with PROXY protocol v1 parsing enabled are vulnerable to remote memory exhaustion. An unauthenticated attacker can open a TCP connection and send bytes without CRLF, causing Puma to continuously append to an internal buffer, leading to unbounded memory growth and CPU usage. This may result in process or container out-of-memory conditions or degraded availability. The vulnerability only affects Puma servers configured with 'set_remote_address proxy_protocol: :v1'.

References

Community reviews

Loading reviews…