CVE-2026-48059

HIGHCVSS 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 55% 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: adp:redhat-sadp, epss
Trending — Patch released this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, the HAProxy PROXY protocol v2 codec in netty leaks native or heap memory on every connection when a client sends a syntactically valid header containing nested PP2_TYPE_SSL TLVs (type-length-value records) at depth two or greater. The leak occurs on the successful parse path — no exception is thrown, the message fires downstream, the decoder removes itself, and the application releases the HAProxyMessage normally. Yet the underlying cumulation buffer (a pooled, potentially direct ByteBuf allocated by the channel) remains permanently pinned. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
44.7%
KEV
Not listed

Published

June 11, 2026

Last Modified

July 6, 2026

Advisory Details (3)

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

[HAProxy] Unbalanced Reference Count in Nested PP2_TYPE_SSL TLV Parsing Leads to Memory Exhaustion · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-h2qv-fj59-j46j
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

Vendor Advisories for CVE-2026-48059(5)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnetty-codec-haproxy2026-07-02redhat

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

(1 across 1 ecosystem)
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 32× in last 7d / 122× 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 122 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48059?
CVE-2026-48059 is a high vulnerability published on June 11, 2026. Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, the HAProxy PROXY protocol v2 codec in netty leaks native or heap memory on every connection when a client sends a syntactically valid header containing nested…
When was CVE-2026-48059 disclosed?
CVE-2026-48059 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48059 actively exploited?
CVE-2026-48059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 44.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48059?
CVE-2026-48059 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-48059?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48059, 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-48059

Explore →

Is Your Infrastructure Affected by CVE-2026-48059?

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

Start Free Scan →Browse All CVEs