CVE-2026-65059: Libfurl perl · Furl versions through 3.15 for Perl allow memory exhaustion via unbounded decompression
Affects libfurl-perlSource GCVE Database
Not known to be exploited.
Data as of 5 Nov 2026, 12:34 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10libfurl-perlpkg:deb/ubuntu/libfurl-perl?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlibfurl-perlpkg:deb/ubuntu/libfurl-perl?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlibfurl-perlpkg:deb/ubuntu/libfurl-perl?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlibfurl-perlpkg:deb/ubuntu/libfurl-perl?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSlibfurl-perlpkg:deb/ubuntu/libfurl-perl?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSlibfurl-perlpkg:deb/ubuntu/libfurl-perl?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2026-65059 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-65059 (opens in a new tab)
- lists.security.metacpan.org/cve-announce/msg/44834406/ (opens in a new tab)
- github.com/tokuhirom/Furl/pull/139 (opens in a new tab)
- metacpan.org/release/SYOHEX/Furl-3.15/source/lib/Furl/ZlibStream.pm (opens in a new tab)
- openwall.com/lists/oss-security/2026/11/02/5 (opens in a new tab)