Description
Reverse::Proxy versions before 0.04 for Perl allow HTTP request smuggling via a percent-decoded PATH_INFO written unencoded to the upstream request line.

PSGI hands PATH_INFO to an application percent-decoded, so a %XX sequence in the client URL has become a raw byte by the time the proxy sees it. The proxy appends that byte string to the upstream base URL, and for an Upgrade tunnel writes it into a request line it serializes itself, re-encoding nothing in either path. The HTTP client that sends the resulting URL does not validate the target either. A path containing %0d%0a therefore arrives at the upstream as a CRLF that ends the request line, and a decoded space, '?' or '#' truncates it the same way.

Everything the client writes after the CRLF is read by the upstream as a second request. On the buffered path it arrives on a keep-alive connection the proxy pools and reuses for other clients. Its method, path and headers are all chosen by the client, and the upstream attributes it to the proxy, so it reaches upstream paths that the proxy's own routing does not expose.
Published: 2026-08-23
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: HTTP request smuggling that permits injection of arbitrary upstream requests
Action: Patch Upgrade
AI Analysis

Impact

Reverse-Proxy versions before 0.04 for Perl allow an attacker to send a crafted HTTP request containing percent‑encoded characters in the URL path. The proxy decodes these bytes before appending them to the upstream request line, so a sequence such as %0d%0a becomes an actual CRLF character. The CRLF terminates the upstream request line, and the following client data is interpreted as a second, independent HTTP request. This enables an attacker to send arbitrary requests to the upstream application while the upstream believes the requests originated from the proxy.

Affected Systems

The flaw is present in all releases of Reverse-Proxy older than 0.04, distributed in the Perl module Reverse::Proxy from the LNATION distribution. Upgrading to version 0.04 or later eliminates the vulnerability.

Risk and Exploitability

Any remote client that can send HTTP requests to the affected proxy can exploit the flaw; no local privileges or special conditions are required. The CVSS score of 5.3 indicates moderate severity, and the EPSS score is less than 1%, suggesting a low probability of exploitation. The vulnerability is not listed in CISA’s KEV catalog. Request smuggling is a well‑known technique that can allow attackers to access routes or services not normally exposed through the proxy. The attack path is straightforward once a percent‑encoded CRLF sequence is used, making the potential impact significant if the upstream service is sensitive to arbitrary requests.

Generated by OpenCVE AI on August 26, 2026 at 03:39 UTC.

Remediation

Vendor Solution

Upgrade to Reverse-Proxy 0.04 or later.


OpenCVE Recommended Actions

  • Upgrade Reverse-Proxy to version 0.04 or later.
  • Validate or encode percent‑decoded characters in PATH_INFO before forwarding to the upstream server, preventing CRLF injection.
  • Monitor proxy and upstream logs for unexpected second requests, CRLF sequences, or anomalous request patterns indicative of request smuggling.

Generated by OpenCVE AI on August 26, 2026 at 03:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 25 Aug 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 24 Aug 2026 21:30:00 +0000

Type Values Removed Values Added
First Time appeared Lnation
Lnation reverse Proxy
Vendors & Products Lnation
Lnation reverse Proxy

Sun, 23 Aug 2026 21:30:00 +0000

Type Values Removed Values Added
References

Sun, 23 Aug 2026 18:30:00 +0000

Type Values Removed Values Added
Description Reverse::Proxy versions before 0.04 for Perl allow HTTP request smuggling via a percent-decoded PATH_INFO written unencoded to the upstream request line. PSGI hands PATH_INFO to an application percent-decoded, so a %XX sequence in the client URL has become a raw byte by the time the proxy sees it. The proxy appends that byte string to the upstream base URL, and for an Upgrade tunnel writes it into a request line it serializes itself, re-encoding nothing in either path. The HTTP client that sends the resulting URL does not validate the target either. A path containing %0d%0a therefore arrives at the upstream as a CRLF that ends the request line, and a decoded space, '?' or '#' truncates it the same way. Everything the client writes after the CRLF is read by the upstream as a second request. On the buffered path it arrives on a keep-alive connection the proxy pools and reuses for other clients. Its method, path and headers are all chosen by the client, and the upstream attributes it to the proxy, so it reaches upstream paths that the proxy's own routing does not expose.
Title Reverse::Proxy versions before 0.04 for Perl allow HTTP request smuggling via a percent-decoded PATH_INFO written unencoded to the upstream request line
Weaknesses CWE-444
CWE-93
References

Subscriptions

Lnation Reverse Proxy
cve-icon MITRE

Status: PUBLISHED

Assigner: CPANSec

Published:

Updated: 2026-08-25T19:30:38.767Z

Reserved: 2026-08-18T15:10:32.506Z

Link: CVE-2026-75922

cve-icon Vulnrichment

Updated: 2026-08-23T21:05:13.636Z

cve-icon NVD

Status : Deferred

Published: 2026-08-23T19:16:28.930

Modified: 2026-08-26T16:51:19.490

Link: CVE-2026-75922

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-26T03:45:03Z

Weaknesses
  • CWE-444

    Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

  • CWE-93

    Improper Neutralization of CRLF Sequences ('CRLF Injection')