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
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jul 6, 2026
No patch confirmed yet.
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
generic
https://lists.apache.org/thread/zmxh1pl2zohov5ntdh4lt85gfrlchgpy

Vendor Advisories for CVE-2026-54399(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
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

(7 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
httpcomponents-core4.4.16-1——
httpcomponents-core55.2.1-1 ... 5.4.2-2 (7 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
httpcomponents-core4.4.16-1——
httpcomponents-core55.2.2-1 ... 5.4.2-2 (6 versions)——
Debian:14(2)
PackageVulnerable rangeFixed inDependents
httpcomponents-core4.4.16-1——
httpcomponents-core55.2.2-1 ... 5.4.2-2 (6 versions)——
Debian:11(1)
PackageVulnerable rangeFixed inDependents
httpcomponents-core4.4.14-1, 4.4.14-2, 4.4.15-1, 4.4.16-1——

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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 in the National Vulnerability Database 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 1% probability of exploitation in the next 30 days, which ranks it in the top 55.5% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54399, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs