Skip to main content
VulnerabilityPublished

CVE-2026-65059: Furl versions through 3.15 for Perl allow memory exhaustion via unbounded decompression of HTTP

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-65059· High

Not known to be exploited.

Data as of 2 Nov 2026, 19:17 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
FurlAffected
  • <=3.15
Fixed in–
CPANFurlpkg:cpan/FurlOther threatsAffected
  • <=3.15
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should avoid using Furl versions through 3.15 with untrusted HTTP servers or on unencrypted connections. Consider using streaming response methods like write_file or write_code that do not hold the entire decompressed response in memory. Monitor vendor advisories for any forthcoming patches or updates addressing this issue.

Description

Furl versions through 3.15 for Perl have a vulnerability that allows memory exhaustion via unbounded decompression of HTTP responses. The library inflates compressed response bodies without limiting the decompressed size, which can cause the client to exhaust memory and crash. This occurs regardless of whether the request asked for compression, and no option exists to cap the decompressed output size. The vulnerability can be triggered by a malicious server or an attacker on a plain HTTP connection sending a small compressed response that expands excessively.

References

Community reviews

Loading reviews…