CVE-2026-64607

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-07-31. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 31, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated Jul 31, 2026
Patch available.

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhathttpclient5-parent2026-09-24redhat
redhatquarkus-apache-httpclient2026-09-03redhat
redhatocp-tools-4/jenkins-rhel9:17871246322026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871246352026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871249252026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871253112026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871247792026-08-26redhat
redhatocp-tools-4/jenkins-rhel8:17866286672026-08-26redhat
redhatocp-tools-4/jenkins-rhel8:17866286812026-08-26redhat
redhatocp-tools-4/jenkins-rhel8:17865335612026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871251662026-08-26redhat
redhatocp-tools-4/jenkins-rhel8:17865335652026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871250692026-08-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 5 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
commons-httpclient3.1-16
  • every version on: no fix on record
—
httpcomponents-client4.5.13-2, 4.5.13-3, 4.5.14-1
  • every version on: no fix on record
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
commons-httpclient3.1-16
  • every version on: no fix on record
—
httpcomponents-client4.5.14-1
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
commons-httpclient3.1-16
  • every version on: no fix on record
—
httpcomponents-client4.5.14-1
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
commons-httpclient3.1-16
  • every version on: no fix on record
—
httpcomponents-client4.5.14-1
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.httpcomponents.client5:httpclient55.0 ... 5.6.2 (46 versions)
  • 5.0-alpha1 up to 5.6.3: fixed in 5.6.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 139 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 06:32 UTCEG score recompute
  3. 2026-10-04 06:32 UTCVendor advisory
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 17:56 UTCEPSS rescore
  6. 2026-10-02 16:51 UTCEG score recompute
  7. 2026-10-02 16:51 UTCVendor advisory
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 02:48 UTCEG score recompute
  10. 2026-10-01 02:48 UTCVendor advisory
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-29 06:50 UTCEG score recompute
  13. 2026-09-29 06:50 UTCVendor advisory
  14. 2026-09-28 13:51 UTCEPSS rescore
  15. 2026-09-27 18:56 UTCEG score recompute
  16. 2026-09-27 18:56 UTCVendor advisory
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-24 09:37 UTCEG score recompute
  19. 2026-09-24 09:37 UTCVendor advisory
  20. 2026-09-23 17:54 UTCEPSS rescore
  21. 2026-09-23 08:42 UTCEG score recompute
  22. 2026-09-23 08:42 UTCVendor advisory
  23. 2026-09-22 07:46 UTCEG score recompute
  24. 2026-09-22 07:46 UTCVendor advisory
  25. 2026-09-20 20:16 UTCEPSS rescore
Show 75 more
  1. 2026-09-19 23:43 UTCEG score recompute
  2. 2026-09-19 23:43 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 07:59 UTCEG score recompute
  5. 2026-09-18 07:59 UTCVendor advisory
  6. 2026-09-17 07:07 UTCEG score recompute
  7. 2026-09-17 07:07 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:29 UTCEG score recompute
  10. 2026-09-16 05:29 UTCVendor advisory
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-14 11:47 UTCEG score recompute
  13. 2026-09-14 11:47 UTCVendor advisory
  14. 2026-09-13 10:56 UTCEG score recompute
  15. 2026-09-13 10:56 UTCVendor advisory
  16. 2026-09-12 09:38 UTCEG score recompute
  17. 2026-09-12 09:38 UTCVendor advisory
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-11 09:37 UTCEPSS rescore
  20. 2026-09-11 08:47 UTCEG score recompute
  21. 2026-09-11 08:47 UTCVendor advisory
  22. 2026-09-10 07:56 UTCVendor advisory
  23. 2026-09-09 07:05 UTCEG score recompute
  24. 2026-09-09 07:05 UTCVendor advisory
  25. 2026-09-08 22:01 UTCEPSS rescore
  26. 2026-09-07 21:38 UTCEG score recompute
  27. 2026-09-07 21:38 UTCVendor advisory
  28. 2026-09-07 16:01 UTCEPSS rescore
  29. 2026-09-06 20:47 UTCEG score recompute
  30. 2026-09-06 20:47 UTCVendor advisory
  31. 2026-09-06 13:47 UTCEPSS rescore
  32. 2026-09-05 18:46 UTCEG score recompute
  33. 2026-09-05 18:46 UTCVendor advisory
  34. 2026-09-05 15:31 UTCEPSS rescore
  35. 2026-09-04 11:21 UTCEG score recompute
  36. 2026-09-04 11:21 UTCVendor advisory
  37. 2026-09-04 05:07 UTCEPSS rescore
  38. 2026-09-03 09:13 UTCEG score recompute
  39. 2026-09-02 14:12 UTCEPSS rescore
  40. 2026-09-02 08:11 UTCEG score recompute
  41. 2026-09-01 13:54 UTCEPSS rescore
  42. 2026-09-01 04:40 UTCEPSS rescore
  43. 2026-08-30 23:13 UTCEG score recompute
  44. 2026-08-30 19:17 UTCEPSS rescore
  45. 2026-08-30 01:22 UTCEPSS rescore
  46. 2026-08-29 22:22 UTCEG score recompute
  47. 2026-08-28 21:42 UTCEPSS rescore
  48. 2026-08-28 06:24 UTCEG score recompute
  49. 2026-08-27 05:18 UTCEG score recompute
  50. 2026-08-26 14:47 UTCEPSS rescore
  51. 2026-08-26 04:25 UTCEG score recompute
  52. 2026-08-25 13:49 UTCEPSS rescore
  53. 2026-08-25 03:14 UTCEG score recompute
  54. 2026-08-23 01:15 UTCEG score recompute
  55. 2026-08-23 00:19 UTCEPSS rescore
  56. 2026-08-22 00:24 UTCEG score recompute
  57. 2026-08-21 23:49 UTCEPSS rescore
  58. 2026-08-20 23:32 UTCEG score recompute
  59. 2026-08-20 22:55 UTCEPSS rescore
  60. 2026-08-19 22:42 UTCEG score recompute
  61. 2026-08-19 17:04 UTCEPSS rescore
  62. 2026-08-18 21:51 UTCEG score recompute
  63. 2026-08-18 13:48 UTCEPSS rescore
  64. 2026-08-17 21:00 UTCEG score recompute
  65. 2026-08-17 13:47 UTCEPSS rescore
  66. 2026-08-16 20:10 UTCEG score recompute
  67. 2026-08-16 14:56 UTCEPSS rescore
  68. 2026-08-15 19:20 UTCEG score recompute
  69. 2026-08-15 01:30 UTCEPSS rescore
  70. 2026-08-14 18:29 UTCEG score recompute
  71. 2026-08-13 22:00 UTCEPSS rescore
  72. 2026-08-13 17:38 UTCGHSA enrichment
  73. 2026-08-13 16:38 UTCGHSA enrichment
  74. 2026-08-13 09:21 UTCGHSA enrichment
  75. 2026-08-12 16:11 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-64607?
CVE-2026-64607 is a medium vulnerability published on July 31, 2026. 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…
When was CVE-2026-64607 disclosed?
CVE-2026-64607 was first published on July 31, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64607 actively exploited?
CVE-2026-64607 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64607?
CVE-2026-64607 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-64607?
A fix for CVE-2026-64607 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64607 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64607

Explore →

Is Your Infrastructure Affected by CVE-2026-64607?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.