Skip to main content
VulnerabilityPublished Updated

CVE-2026-84382: HTTPX2 · Streaming response decompression does not bound peak memory (decompression amplification)

Affects rapid-mlxSource GCVE Database

0
Compare
Authoritative record:CVE-2026-84382· High 7.5

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

Data as of 1 Nov 2026, 00:35 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.12.16
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Sep 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 31 Oct 2026.

What to do

Upgrade rapid-mlx to 0.12.16.

Affected software

ProductAffectedFixed in
Homebrewrapid-mlxpkg:brew/rapid-mlxOther threatsAffected
  • >=0.11.3 <0.12.16
Fixed in
  • 0.12.16

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

AI-suggested

Upgrade HTTPX2 to version 0.12.16 or later. The fixed version decompresses response data incrementally using bounded buffers, preventing large intermediate memory allocations and mitigating decompression amplification attacks.

Description

HTTPX2 versions prior to 0.12.16 decompress streaming response bodies fully per network read, causing large intermediate memory allocations. This decompression amplification can lead to significant memory pressure or out-of-memory termination when processing malicious compressed responses from untrusted servers. The issue affects compressed responses using gzip, deflate, brotli, or zstd encodings. The vulnerability is fixed in HTTPX2 version 0.12.16, which implements incremental decompression with bounded buffers.

References

Community reviews

Loading reviews…