CVE-2026-48059

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 52% 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, nvd
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. 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)
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
48%
KEV
Not listed

Published

June 11, 2026

Last Modified

August 13, 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(13)

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

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 24× in last 7d / 101× 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 208 total refreshes for this CVE.

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

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 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-48059 actively exploited?
CVE-2026-48059 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 52.5% of all scored CVEs.
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