CVE-2026-64607: Apache HttpComponents Client: Connection Leak on Content-Encoding Decode Error Leads to Pool Exhaustion DoS

Published Jul 31, 2026
·
Updated

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.

Affected Software

2 affected components
Apache HttpComponents Client>=5.0-alpha1<=5.6.2
Apache HttpClient>=5.0.0<5.6.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache HttpComponents Client to a version that resolves this vulnerability.

    Fixed in 5.6.2Patch CVE-2026-64607

Event History

Jul 31, 2026
CVE Published
via MITRE·10:12 AM
Data Sourced
via MITRE·10:12 AM
DescriptionWeakness
Data Sourced
via NVD·11:17 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-64607?

CVE-2026-64607 has a risk rating of 35.

2

How do I fix CVE-2026-64607?

To fix CVE-2026-64607, update to the latest version of Apache HttpComponents Client that addresses the connection leak issue.

3

What systems are affected by CVE-2026-64607?

CVE-2026-64607 affects the Apache HttpComponents Client based on the classic I/O model.

4

What is the impact of CVE-2026-64607?

CVE-2026-64607 can lead to connection leaks and exhaustion of the connection pool, resulting in a denial of service (DoS) condition.

5

Does CVE-2026-64607 affect asynchronous I/O models?

No, CVE-2026-64607 does not affect the HttpClient based on the asynchronous I/O model.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203