Furl 3.15 fixes memory exhaustion in Perl HTTP decompression
Furl versions through 3.15 allow memory exhaustion via unbounded decompression of HTTP responses (CVE-2026-65059).
40
CVE-2026-65059
Memory exhaustion in Furl Perl HTTP decompression < 3.16
- CVSS 3.1
- 7.5 high
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
Furl versions through 3.15 for Perl allow memory exhaustion via unbounded decompression of HTTP responses. A malicious server or attacker on plain HTTP can send a small compressed response that expands to exhaust client memory and crash the process. Affected are Perl apps using Furl.
What to do: Upgrade Furl to a version after 3.15; no workaround given
| Product | Affected |
|---|---|
| Perl Furl | through 3.15 |
Estimated exposure
No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
Furl versions before 3.16 for Perl allow memory exhaustion via unbounded decompression of HTTP responses. Furl inflates a response body sent with a gzip, x-gzip or deflate Content-Encoding and appends the output to the response string with no size limit. It does this whether or not the request asked for compression, and no option caps the decompressed size. Responses read with write_file or write_code are streamed rather than held in memory. A malicious server, or an attacker on a plain HTTP connection, can send a small compressed response that expands to exhaust the client's memory and end the process.
- Weakness
- CWE-409
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H