CVE-2026-54399

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Uncontrolled Resource Consumption vulnerability in the HTTP/1.1 message parser in Apache HttpComponents Core (5.4.2 and earlier, 5.5-beta1 and earlier) allows an remote attacker to cause a denial of service through memory exhaustion by sending messages with excessive number of headers / excessive header length

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
39
EG Risk 39/100

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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

Published

July 1, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jul 6, 2026
Patch available.
generic

oss-security - CVE-2026-54399: Apache HttpComponents Core: Unbounded HTTP Header/Line Length in Default Configuration

http://www.openwall.com/lists/oss-security/2026/07/01/4

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcryostat/cryostat-rhel9:4.2.0-142026-09-16redhat
redhatdevspaces/pluginregistry-rhel9:17877597232026-09-01redhat
redhatrhaiis/vllm-cuda-rhel9:17878605802026-08-31redhat
redhatocp-tools-4/jenkins-rhel9:17871247792026-08-26redhat
redhatocp-tools-4/jenkins-rhel8:17866286812026-08-26redhat
redhatocp-tools-4/jenkins-rhel8:17866286672026-08-26redhat
redhatocp-tools-4/jenkins-rhel8:17865335652026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871246352026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871246322026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871250692026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871251662026-08-26redhat
redhatocp-tools-4/jenkins-rhel8:17865335612026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871249252026-08-26redhat
redhatocp-tools-4/jenkins-rhel9:17871253112026-08-26redhat
redhathttpcore52026-08-13redhat
redhatpatch2026-07-30redhat
redhathttpcore2026-07-30redhat

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

(8 across 5 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
httpcomponents-core4.4.16-1
  • every version on: no fix on record
—
httpcomponents-core55.2.1-1 ... 5.4.4-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
httpcomponents-core4.4.16-1
  • every version on: no fix on record
—
httpcomponents-core55.2.2-1 ... 5.4.4-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
httpcomponents-core4.4.16-1
  • every version on: no fix on record
—
httpcomponents-core55.2.2-1 ... 5.4.2-2 (6 versions)
  • every version up to 5.4.3-1: fixed in 5.4.3-1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
httpcomponents-core4.4.14-1, 4.4.14-2, 4.4.15-1, 4.4.16-1
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.httpcomponents.core5:httpcore55.5-alpha1, 5.5-beta1
  • every version up to 5.4.3: fixed in 5.4.3
  • 5.5-alpha1 up to 5.5-beta2: fixed in 5.5-beta2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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 256 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-54399?
CVE-2026-54399 is a high vulnerability published on July 1, 2026. Uncontrolled Resource Consumption vulnerability in the HTTP/1.1 message parser in Apache HttpComponents Core (5.4.2 and earlier, 5.5-beta1 and earlier) allows an remote attacker to cause a denial of service through memory exhaustion by sending messages with excessive number of headers / excessive…
When was CVE-2026-54399 disclosed?
CVE-2026-54399 was first published on July 1, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54399 actively exploited?
CVE-2026-54399 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54399?
CVE-2026-54399 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-54399?
A fix for CVE-2026-54399 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54399 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-54399

Explore →

Is Your Infrastructure Affected by CVE-2026-54399?

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