Advisory

GHSA-2vqw-3mp8-cgmx

Also known as: CVE-2026-47737

Summary

Puma PROXY Protocol v1 Accepts Repeated Protocol Headers on Persistent Connections

Details

Impact

Puma is vulnerable to source IP spoofing when set_remote_address proxy_protocol: :v1 is enabled and persistent connections are used.

PROXY protocol v1 is a connection-level protocol. Support was added to Puma in v5.5.0. A proxy sends one PROXY header at the beginning of a TCP connection, before any HTTP data. Puma incorrectly re-parsed PROXY protocol headers after each keep-alive request on the same connection. An attacker able to send HTTP requests through a trusted proxy could therefore inject a second PROXY header between HTTP requests. Puma would treat the injected header as authoritative for the next request and overwrite REMOTE_ADDR.

This can mislead applications or middleware that use REMOTE_ADDR for security decisions, rate limiting, auditing, or allow/deny lists.

Only deployments that explicitly enable PROXY protocol v1 are affected, and will have set:

set_remote_address proxy_protocol: :v1

Puma's default configuration is not affected. Deployments that do not use persistent connections to Puma are also not expected to be affected by this issue.

Patches

Users should upgrade to versions 7.2.1 or 8.0.2.

Workarounds

Disable PROXY protocol v1 parsing if it is not required:

   # remove/comment this:
   # set_remote_address proxy_protocol: :v1

Users can also disable persistent connections to Puma, for example:

enable_keep_alives false

References

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-06-09 00:09 UTC
Modified
2026-11-02 22:15 UTC

Affected packages and fixes

puma

RubyGems · All systems

Affected

  • introduced 8.0.0, fixed 8.0.2 (ecosystem)

Fixed versions

8.0.2

Fix

The export has no generic command for this ecosystem.

puma

RubyGems · All systems

Affected

  • introduced 5.5.0, fixed 7.2.1 (ecosystem)

Fixed versions

7.2.1

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences