Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2026-64607 — httpclient5

MEDIUMFix: apache/httpcomponents-client@55733f4

CVE-2026-64607 is a medium-severity (CVSS 5.3) CWE-772 vulnerability in org.apache.httpcomponents.client5:httpclient5. A fix is available for org.apache.httpcomponents.client5:httpclient5 — see the affected versions and patch details below.

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

Also known asGHSA-hjcp-jmpx-g3qm
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-64607.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk
0.00%0.33%0.65%0.98%0.2%0.5%0.5%0.5%Aug 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-64607 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
☕org.apache.httpcomponents.client5:httpclient5

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.httpcomponents.client5:httpclient5≥ 5.0-alpha1&&< 5.6.35.6.3org.apache.httpcomponents.client5:httpclient5:5.6.3

Affected Products

1 product · 1 configurations
Application
httpclientapache
≥ 5.0.0 && < 5.6.3
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.httpcomponents.client5:httpclient5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.httpcomponents.client5:httpclient5 to 5.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-64607 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This is an Important flaw in Apache HttpComponents Client's classic I/O model, where an invalid `Content-Encoding` header in a response can prevent proper connection release. This connection leak can exhaust the connection pool, leading to a denial of service for applications utilizing the affected client. The…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Source: Red Hat security advisory for CVE-2026-64607 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Build of Apache Camel 3.33 for Quarkus 3.33.3.SP1httpclient5RHSA-2026:63302
Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16httpclient5RHSA-2026:71675
Red Hat build of Quarkus 3.27.5.SP1quarkus-apache-httpclientRHSA-2026:62515
OpenShift Developer Tools and Services 4.12ocp-tools-4/jenkins-rhel8:1786628667RHSA-2026:60247
OpenShift Developer Tools and Services 4.13ocp-tools-4/jenkins-rhel8:1786628681RHSA-2026:60249
OpenShift Developer Tools and Services 4.14ocp-tools-4/jenkins-rhel8:1786533561RHSA-2026:60248
OpenShift Developer Tools and Services 4.15ocp-tools-4/jenkins-rhel8:1786533565RHSA-2026:60239
OpenShift Developer Tools and Services 4.16ocp-tools-4/jenkins-rhel9:1787125166RHSA-2026:60251

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-64607 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2026-64607: httpclient5 — Fixed in 5.6.3