renovate-bot opened a new pull request, #6746:
URL: https://github.com/apache/jmeter/pull/6746

   This PR contains the following updates:
   
   | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | 
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
   |---|---|---|---|
   | [org.apache.httpcomponents.client5:httpclient5](https://hc.apache.org/) 
([source](https://redirect.github.com/apache/httpcomponents-client)) | `5.5.1` 
→ `5.6.3` | 
![age](https://developer.mend.io/api/mc/badges/age/maven/org.apache.httpcomponents.client5:httpclient5/5.6.3?slim=true)
 | 
![confidence](https://developer.mend.io/api/mc/badges/confidence/maven/org.apache.httpcomponents.client5:httpclient5/5.5.1/5.6.3?slim=true)
 |
   
   ---
   
   ### Apache HttpComponents Client: Connection Leak on Content-Encoding Decode 
Error Leads to Pool Exhaustion DoS
   [CVE-2026-64607](https://nvd.nist.gov/vuln/detail/CVE-2026-64607) / 
[GHSA-hjcp-jmpx-g3qm](https://redirect.github.com/advisories/GHSA-hjcp-jmpx-g3qm)
   
   <details>
   <summary>More information</summary>
   
   #### Details
   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
   - CVSS Score: 5.3 / 10 (Medium)
   - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`
   
   #### References
   - 
[https://nvd.nist.gov/vuln/detail/CVE-2026-64607](https://nvd.nist.gov/vuln/detail/CVE-2026-64607)
   - 
[https://lists.apache.org/thread/qqfzo3fqcdk4l5496vz95ppvl4ty511q](https://lists.apache.org/thread/qqfzo3fqcdk4l5496vz95ppvl4ty511q)
   - 
[https://github.com/apache/httpcomponents-client/commit/55733f4121f7ba26ddf04fe12739d9c15962cb94](https://redirect.github.com/apache/httpcomponents-client/commit/55733f4121f7ba26ddf04fe12739d9c15962cb94)
   - 
[https://github.com/apache/httpcomponents-client/commit/ebac9512f555c4a355cad3f59ef2db69b597cc97](https://redirect.github.com/apache/httpcomponents-client/commit/ebac9512f555c4a355cad3f59ef2db69b597cc97)
   - 
[https://github.com/apache/httpcomponents-client/releases/tag/rel/v5.6.3](https://redirect.github.com/apache/httpcomponents-client/releases/tag/rel/v5.6.3)
   - 
[https://github.com/apache/httpcomponents-client/releases/tag/rel/v5.7-alpha1](https://redirect.github.com/apache/httpcomponents-client/releases/tag/rel/v5.7-alpha1)
   - 
[http://www.openwall.com/lists/oss-security/2026/08/13/5](http://www.openwall.com/lists/oss-security/2026/08/13/5)
   - 
[https://github.com/advisories/GHSA-hjcp-jmpx-g3qm](https://redirect.github.com/advisories/GHSA-hjcp-jmpx-g3qm)
   
   This data is provided by the [GitHub Advisory 
Database](https://redirect.github.com/advisories/GHSA-hjcp-jmpx-g3qm) ([CC-BY 
4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
   </details>
   
   ---
   
   ### Release Notes
   
   <details>
   <summary>apache/httpcomponents-client 
(org.apache.httpcomponents.client5:httpclient5)</summary>
   
   ### 
[`v5.6.3`](https://redirect.github.com/apache/httpcomponents-client/compare/rel/v5.6.2...5.6.3-RC1)
   
   ### 
[`v5.6`](https://redirect.github.com/apache/httpcomponents-client/blob/HEAD/RELEASE_NOTES.txt#Release-56-ALPHA1)
   
   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.
   
   </details>
   
   ---
   
   ### 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.
   
   ---
   
    - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this 
box
   
   ---
   
   This PR was generated by [Mend Renovate](https://mend.io/renovate/). View 
the [repository job log](https://developer.mend.io/github/apache/jmeter).
   
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4yOS41IiwidXBkYXRlZEluVmVyIjoiNDQuMjkuNSIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to