CVE-2026-85721

AsyncHttpClient: Unbounded HTTP/1.1 response decompression enables a decompression-bomb denial of service

Published Sep 17, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.0.0 until 2.16.1 and 3.0.12, automatic response decompression on the HTTP/1.1 path uses ChannelManager.newHttpContentDecompressor() to install Http1ContentDecompressor without a cumulative output-size limit. A hostile or compromised server, or an attacker who can alter a response in transit, can send a small gzip, deflate, or snappy response that expands across chunks until the client exhausts its heap and raises OutOfMemoryError; brotli and zstd are also affected when their optional codecs are present. In versions 3.0.8 through 3.0.10, the HTTP/2 decompressor is also unbounded, so switching protocols does not mitigate the issue on those releases. A limit applied to each decode call is insufficient because the response can be delivered as many small chunks, so the fixed implementation tracks total decompressed bytes for the whole response. This issue is fixed in versions 2.16.1 and 3.0.12.

Analysis

AI-generated

Technical impact

This vulnerability arises because the AsyncHttpClient library performs automatic HTTP/1.1 response decompression without an overall output-size limit. A malicious server or a manipulated network response can send a small compressed payload that expands into a disproportionately large uncompressed body. The decompressor consumes the client’s heap until an OutOfMemoryError is thrown, effectively denying service to the affected application. The flaw maps to resource exhaustion weaknesses.

Affected Systems

The flaw affects the AsyncHttpClient library in versions 2.0.0 through 2.16.0 and 3.0.0 through 3.0.11. The HTTP/2 decompressor was also unbounded in releases 3.0.8 to 3.0.10, meaning simply switching protocols does not mitigate the issue on those releases. The issue was addressed in versions 2.16.1 and 3.0.12, which contain the fixed decompressor implementation.

Risk and Exploitability

The CVSS score of 7.5 indicates a medium to high severity impact, while the EPSS score of less than 1% signals a very low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a malicious HTTP response delivered over the network; the attacker must control or alter the server response to supply large decompressed data. Exploitation requires the target application to use the vulnerable library and to process external HTTP responses without additional safeguards.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the AsyncHttpClient library to version 2.16.1 or later, or to 3.0.12 or newer, which contains the fixed decompressor implementation.
  • If an immediate library upgrade cannot be performed, consider reducing the JVM heap available to the application or implementing network-level filtering to block excessively large HTTP responses as a temporary mitigator.
  • Configure the library to disable automatic response decompression and handle decompression manually with an explicitly enforced size limit on the total number of decompressed bytes.

Generated by OpenCVE AI on September 24, 2026 at 02:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-7grg-jcf7-rpmx AsyncHttpClient's unbounded HTTP/1.1 response decompression enables a decompression-bomb denial of service
History
Type Values Removed Values Added
First Time appeared Asynchttpclient Project
Asynchttpclient Project async-http-client
Vendors & Products Asynchttpclient Project
Asynchttpclient Project async-http-client
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.0.0 until 2.16.1 and 3.0.12, automatic response decompression on the HTTP/1.1 path uses ChannelManager.newHttpContentDecompressor() to install Http1ContentDecompressor without a cumulative output-size limit. A hostile or compromised server, or an attacker who can alter a response in transit, can send a small gzip, deflate, or snappy response that expands across chunks until the client exhausts its heap and raises OutOfMemoryError; brotli and zstd are also affected when their optional codecs are present. In versions 3.0.8 through 3.0.10, the HTTP/2 decompressor is also unbounded, so switching protocols does not mitigate the issue on those releases. A limit applied to each decode call is insufficient because the response can be delivered as many small chunks, so the fixed implementation tracks total decompressed bytes for the whole response. This issue is fixed in versions 2.16.1 and 3.0.12.
Title AsyncHttpClient: Unbounded HTTP/1.1 response decompression enables a decompression-bomb denial of service
Weaknesses CWE-400
CWE-409
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-409

    Improper Handling of Highly Compressed Data (Data Amplification)

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 17, 2026, 5:22 PM
Reserved
Sep 4, 2026, 2:45 PM
Status
Awaiting Analysis
Published
Sep 17, 2026, 4:18 PM
Modified
Sep 30, 2026, 5:43 PM
Severity
Important
Public date
Sep 17, 2026, 3:55 PM