CVE-2026-44893

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
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.

Netty is a network application framework for development of protocol servers and clients. In netty-codec-haproxy prior to versions 4.1.135.Final and 4.2.15.Final, when decoding a PP2_TYPE_SSL TLV, HAProxyMessage.readNextTLV() first calls header.retainedSlice(header.readerIndex(), length) and only then reads the 1-byte client field and 4-byte verify field. If the attacker sets the TLV length below 5, the subsequent readByte/readInt throws IndexOutOfBoundsException. HAProxyMessageDecoder only catches HAProxyProtocolException around this call, so the IOOBE propagates and the retained slice on the pooled cumulation buffer is never released. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

June 8, 2026

Last Modified

August 13, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
Patch available. Sources: github_release, github.
github Patch Available

HAProxy SSL TLV parsing leaks retained slice on invalid TLV length · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-cc37-9q2j-3hfv
github_release Patch Available

netty-4.2.15.Final

Patch available: netty/netty netty-4.2.15.Final

https://github.com/netty/netty/releases/tag/netty-4.2.15.Final
github_release Patch Available

netty-4.1.135.Final

Patch available: netty/netty netty-4.1.135.Final

https://github.com/netty/netty/releases/tag/netty-4.1.135.Final

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnetty-codec-haproxy2026-08-12redhat
redhateap7-wildfly-0:7.4.25-2.GA_redhat_00001.1.el7eap2026-08-11redhat
redhatcryostat/jfr-datasource-rhel9:4.2.0-132026-07-29redhat
redhatdevspaces/multicluster-redirector-rhel9:17829890272026-07-08redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (16 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-9 (12 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (8 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
netty1:4.1.48-10 ... 1:4.1.48-16 (7 versions)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.netty:netty-codec-haproxy4.0.29.Final ... 4.1.99.Final (178 versions)4.1.135.Final

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-44893?
CVE-2026-44893 is a high vulnerability published on June 8, 2026. Netty is a network application framework for development of protocol servers and clients. In netty-codec-haproxy prior to versions 4.1.135.Final and 4.2.15.Final, when decoding a PP2TYPESSL TLV, HAProxyMessage.readNextTLV() first calls header.retainedSlice(header.readerIndex(), length) and only…
When was CVE-2026-44893 disclosed?
CVE-2026-44893 was first published in the National Vulnerability Database on June 8, 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-44893 actively exploited?
CVE-2026-44893 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 53.1% of all scored CVEs.
What is the CVSS score of CVE-2026-44893?
CVE-2026-44893 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44893?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44893, 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-44893

Explore →

Is Your Infrastructure Affected by CVE-2026-44893?

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