Skip to main content
No exploitation reported

CVE-2026-65059

Furl versions through 3.15 for Perl allow memory exhaustion via unbounded decompression of HTTP responses

No exploitation reported by the sources we read.

  • Published2026-11-02
  • WeaknessCWE-409

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-0217:01CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As CPANSec, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-02

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • libfurl-perlUbuntu:26.10all versions · no fixed version listed
  • libfurl-perlUbuntu:26.04:LTSall versions · no fixed version listed
  • libfurl-perlUbuntu:24.04:LTSall versions · no fixed version listed
  • libfurl-perlUbuntu:22.04:LTSall versions · no fixed version listed
  • libfurl-perlUbuntu:20.04:LTSall versions · no fixed version listed
  • libfurl-perlUbuntu:18.04:LTSall versions · no fixed version listed
  • libfurl-perlUbuntu:16.04:LTSall versions · no fixed version listed
  • libfurl-perlDebian:14all versions · no fixed version listed

2 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2026-11-02
Last Modified
2026-11-06
NVD status
Deferred
GitHub Advisory
GHSA-m2rh-hmhf-hh5g

Frequently asked questions

What is CVE-2026-65059?

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.

Is CVE-2026-65059 actively exploited?

Active exploitation of CVE-2026-65059 has not been confirmed. Its EPSS score was 0.2% on 2026-11-05, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-65059?

CVE-2026-65059 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running libfurl-perl? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record