A bug in PSL validation logic in Apache HttpClient 5.4.x disables domain checks, affecting cookie management and host name verification. Discovered by the Apache HttpClient team. Fixed in the 5.4.3 release.
HttpClient based on the classic i/o model fails to correctly release the underlying connection back to the connection manager if it encounters an invalid or unsupported Content-Encoding header value in the response message. Please note this defect does not affect HttpClient based on the async i/o model.
This issue affects Apache HttpComponents Client: from 5.0-alpha1 through 5.6.2.
This is the first ALPHA release in the 5.6 release series. It adds several features
such as transport content decompression and content compression for the async transport,
support for Unix sockets, experimental support for SCRAM-SHA-256 authentication scheme,
and Micrometer/OTel observations & metrics.
Commons Compress, Brotli codec, and ZStd codec are optional dependencies and get
wired into the execution pipeline only if present on the classpath.
Notable changes and features included in the 5.6 series:
Unix domain socket support.
Support for pluggable content codecs via Commons-Compress in the classic transport.
(optional).
Support for transparent content decompression and content compression with deflate,
gzip, zstd (optional), and brotli (optional) codecs in the async transport.
Micrometer/OTel observations & metrics (optinal).
Off-lock connection disposal by the classic pooling connection manager. Experimental.
Request Priority support (RFC 9218). Experimental.
Compatibility notes:
As of this version, HttpClient uses BUILTIN HostnameVerificationPolicy by default, delegating
host verification to JSSE security manager. One must explicitly configure the TLS strategy
to continue using the hostname verifier shipped with HttpClient.
Five-second TCP keep-alive is now enabled by default.
This is the first GA release in the 5.5 release series. This release finalizes the 5.5
APIs and adds several experimental features and improvements, such as request multiplexing
over a shared HTTP/2 connection and the Classic API facade acting as a compatibility
bridge between classic I/O client services and the asynchronous message transport used
internally.
Notable changes and features included in the 5.5 series:
Improved conformance to RFC 7616 (HTTP Digest Access Authentication).
The connection pool implementation acts as a caching facade in front of a standard
managed connection pool and shares already leased connections to multiplex message
exchanges over active HTTP/2 connections. Experimental.
Extended Auth API and improved authentication protocol logic to support mutual
authentication.
The Classic API facade now acts as a compatibility bridge between the classic I/O client
services (based on the standard InputStream / OutputStream model) and the asynchronous
message transport used internally. This is experimental.
HTTP/2 support for the Fluent Facade (via Classic API facade). This is experimental.
Compatibility notes:
As of this release, HttpClient does not automatically execute redirects if the original
request manually added headers that are considered sensitive.
Configuration
📅 Schedule: (UTC)
Branch creation
At any time (no schedule defined)
Automerge
At any time (no schedule defined)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
If you want to rebase/retry this PR, check this box
renovate-bot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.2
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.3
Mar 26, 2025
renovate-bot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.3
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.3 [security]
Apr 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Apache HttpClient disables domain checks
CVE-2025-27820 / GHSA-73m2-qfq3-56cx
More informationDetails
A bug in PSL validation logic in Apache HttpClient 5.4.x disables domain checks, affecting cookie management and host name verification. Discovered by the Apache HttpClient team. Fixed in the 5.4.3 release.
Severity
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Apache HttpComponents Client: Connection Leak on Content-Encoding Decode Error Leads to Pool Exhaustion DoS
CVE-2026-64607 / GHSA-hjcp-jmpx-g3qm
More informationDetails
HttpClient based on the classic i/o model fails to correctly release the underlying connection back to the connection manager if it encounters an invalid or unsupported Content-Encoding header value in the response message. Please note this defect does not affect HttpClient based on the async i/o model.
This issue affects Apache HttpComponents Client: from 5.0-alpha1 through 5.6.2.
Severity
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
apache/httpcomponents-client (org.apache.httpcomponents.client5:httpclient5)v5.6.3
v5.6
This is the first ALPHA release in the 5.6 release series. It adds several features
such as transport content decompression and content compression for the async transport,
support for Unix sockets, experimental support for SCRAM-SHA-256 authentication scheme,
and Micrometer/OTel observations & metrics.
Commons Compress, Brotli codec, and ZStd codec are optional dependencies and get
wired into the execution pipeline only if present on the classpath.
Notable changes and features included in the 5.6 series:
Unix domain socket support.
Support for pluggable content codecs via Commons-Compress in the classic transport.
(optional).
Support for transparent content decompression and content compression with deflate,
gzip, zstd (optional), and brotli (optional) codecs in the async transport.
Micrometer/OTel observations & metrics (optinal).
Off-lock connection disposal by the classic pooling connection manager. Experimental.
SCRAM-SHA-256 authentication scheme (RFC 7804). Experimental.
Request Priority support (RFC 9218). Experimental.
Compatibility notes:
As of this version, HttpClient uses BUILTIN HostnameVerificationPolicy by default, delegating
host verification to JSSE security manager. One must explicitly configure the TLS strategy
to continue using the hostname verifier shipped with HttpClient.
Five-second TCP keep-alive is now enabled by default.
v5.5
This is the first GA release in the 5.5 release series. This release finalizes the 5.5
APIs and adds several experimental features and improvements, such as request multiplexing
over a shared HTTP/2 connection and the Classic API facade acting as a compatibility
bridge between classic I/O client services and the asynchronous message transport used
internally.
Notable changes and features included in the 5.5 series:
Improved conformance to RFC 7616 (HTTP Digest Access Authentication).
The connection pool implementation acts as a caching facade in front of a standard
managed connection pool and shares already leased connections to multiplex message
exchanges over active HTTP/2 connections. Experimental.
Extended Auth API and improved authentication protocol logic to support mutual
authentication.
The Classic API facade now acts as a compatibility bridge between the classic I/O client
services (based on the standard InputStream / OutputStream model) and the asynchronous
message transport used internally. This is experimental.
HTTP/2 support for the Fluent Facade (via Classic API facade). This is experimental.
Compatibility notes:
request manually added headers that are considered sensitive.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.