CVE-2026-65059

Furl versions before 3.16 for Perl allow memory exhaustion via unbounded decompression of HTTP responses

Published Nov 2, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
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.

Remediation

Vendor Solution

Upgrade to version 3.16 or later.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description Furl versions through 3.15 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. 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.
Title Furl versions through 3.15 for Perl allow memory exhaustion via unbounded decompression of HTTP responses Furl versions before 3.16 for Perl allow memory exhaustion via unbounded decompression of HTTP responses
References
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Metrics cvssV3_1

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

Type Values Removed Values Added
First Time appeared Tokuhirom
Tokuhirom furl
Vendors & Products Tokuhirom
Tokuhirom furl
Type Values Removed Values Added
Description Furl versions through 3.15 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.
Title Furl versions through 3.15 for Perl allow memory exhaustion via unbounded decompression of HTTP responses
Weaknesses CWE-409
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 10, 2026, 7:47 AM
Reserved
Jul 21, 2026, 3:24 PM
Status
Deferred
Published
Nov 2, 2026, 5:17 PM
Modified
Nov 10, 2026, 8:16 AM