← Back to results
Vulnerability record · public intelligence
CVE-2021-41136
LOW

Puma with proxy which forwards LF characters as line endings could allow HTTP request smuggling

Published Oct 12, 2021 · Updated Nov 3, 2026

Severity · CVSSLOW · Not scored
Known exploitationNot listed
EPSS / likelihood1.20%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

Puma with proxy which forwards LF characters as line endings could allow HTTP request smuggling

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Prior to `puma` version 5.5.0, using `puma` with a proxy which forwards LF characters as line endings could allow HTTP request smuggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client.

Potential impact

Prior to puma version 5.5.0, using puma with a proxy which forwards LF characters as line endings could allow HTTP request smuggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. This behavior (forwarding LF characters as line endings) is very uncommon amongst proxy servers, so we have graded the impact here as "low". Puma is only aware of a single proxy server which has this behavior. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. Patch commit ↗
  4. Patch commit ↗
  5. lists.debian.org ↗
  6. security.gentoo.org ↗
  7. www.debian.org ↗

Record history

Published Oct 12, 2021 · Last refreshed Nov 3, 2026