VulnerabilityPublished 13 Aug 2026Updated 31 Oct 2026

CVE-2026-59939: httplib2 · Decompression Bomb Denial of Service via Unbounded gzip/deflate Response Handling

Affects parsedmarcSource GCVE Database

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 10.2.1 soon.

Data as of 1 Nov 2026, 00:23 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 10.2.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Aug 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 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade parsedmarc to 10.2.1.

Affected software

Product	Affected	Fixed in
Homebrewparsedmarc`pkg:brew/parsedmarc`Other threats	Affected >=8.11.0 <10.2.1	Fixed in 10.2.1

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

AI-suggested

A fix is available in httplib2 version 10.2.1. Users should upgrade to this version or later to mitigate the vulnerability. Until upgraded, avoid making HTTP requests with httplib2 to untrusted or attacker-controlled servers. There is no indication that other mitigations such as configuration changes or workarounds are available.

Description

The httplib2 HTTP client library is vulnerable to a decompression bomb denial of service (DoS) attack via unbounded gzip or deflate response handling. A malicious HTTP server can send a small compressed payload that decompresses to a very large size in memory, causing the client process to run out of memory or crash. This affects any application using httplib2.Http().request() against untrusted or attacker-controlled HTTP endpoints. The vulnerability is fixed in version 10.2.1.

Impact

An attacker controlling or compromising an HTTP server can cause denial of service by sending a maliciously crafted compressed response that decompresses to a very large size, exhausting client memory and causing crashes or process termination. No authentication or special configuration is required. The amplification ratio can exceed 1000x, making small payloads capable of large memory consumption. This impacts availability of applications using vulnerable httplib2 versions when communicating with untrusted servers.

Summary

httplib2 performs unbounded decompression of HTTP response bodies encoded with Content-Encoding: gzip or deflate. The decompression functions gzip.GzipFile.read() and zlib.decompress() are called without limits on decompressed size, allowing a crafted small compressed payload (~150 KB) to expand to an arbitrarily large size (150 MB or more) in memory. This leads to MemoryError or OOM-kill in the client process. The vulnerability exists because there is no maximum decompressed size, streaming decompression with size tracking, or decompression ratio checks. It affects httplib2 versions >=8.11.0 and <10.2.1 and is triggered automatically on any HTTP response with gzip or deflate encoding. The issue is fixed in version 10.2.1.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Nov 2026, 00:23 UTC

Technical details

References

Community reviews

Related threats