Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-h2qv-fj59-j46j

Netty HAProxy: Unbalanced Reference Count in Nested PP2_TYPE_SSL TLV Parsing Leads to Memory Exhaustion

CVSS 8.7 HighEPSS 0.0063 · 50th percentile

Published by the GitHub Advisory Database at 11 Jun 2026, 20:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.netty:netty-codec-haproxyMaven>=4.2.0.Final, <4.2.15.Final || <4.1.135.Final4.2.15.Final, 4.1.135.Final
Identifiers
GHSA-h2qv-fj59-j46j · CVE-2026-48059
Weakness (CWE)
CWE-401 · CWE-1286
Tags
Published
11 Jun 2026
Updated
18 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Netty's netty-codec-haproxy package, versions 4.2.0.Final before 4.2.15.Final and versions before 4.1.135.Final, leaks memory when the HAProxy PROXY protocol v2 decoder parses a valid header containing nested PP2_TYPE_SSL TLVs at depth two or greater. An attacker who can send such headers over a connection can exhaust native or heap memory, since the underlying buffer stays pinned after each successful parse. Upgrade to 4.2.15.Final or 4.1.135.Final, depending on the release line in use.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.7 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0063, the 50th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.