Skip to content
VulniPulse
Sign in
Advisory severityMedium5.5Red Hat Linux

Medium [CVE-2026-59919] Improper CR/LF neutralization in netty-codec-haproxy

This medium-severity Red Hat Linux advisory covers CVE-2026-59919 affecting Cryostat 4, OpenShift Serverless, Red Hat AMQ Broker 7.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-59919 Source published Source updated

VulniPulse record published Record updated

CVE-2026-59919
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

Netty is an asynchronous, event-driven network application framework.

In versions prior to 4.1.136.Final and 4.2.16.Final, Netty's HAProxy encoder ( HAProxyMessageEncoder ) writes AF_UNIX source and destination socket addresses into the HAProxy V1 text protocol without validating them for CRLF characters, so an attacker who controls an AF_UNIX address can inject \r\n sequences and split the single PROXY header into multiple lines.

This is possible because the V1 protocol uses CRLF as its line terminator and, unlike IPv4/IPv6 addresses whose format checks implicitly reject CRLF, AF_UNIX addresses are only validated for length (up to 108 bytes), allowing a forged second PROXY header line that spoofs the client source/destination IP to a downstream server or load balancer.

A flaw was found in the netty-codec-haproxy component, part of the Netty network application framework. This vulnerability allows a remote attacker to perform protocol-level injection attacks by crafting malformed HAProxy protocol frames that contain embedded carriage return (CR) and line feed (LF) sequences.

This can lead to the injection of arbitrary content, potentially disrupting network communication or enabling further attacks. This Moderate flaw in `netty-codec-haproxy` allows for protocol-level injection attacks due to improper neutralization of CR/LF sequences.

Is CVE-2026-59919 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-59919 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-59919?

Upgrade to a fixed release named by Red Hat:

  • 4.1.136
  • 4.2.16

Confirm against the vendor advisory before you patch.

Affected versions
  • < 4.1.136.Final
  • < 4.2.16.Final

Official advisory · high-confidence parse· fetched 3 days ago·verify at source

Fixed versions
  • 4.1.136
  • 4.2.16

Official advisory · high-confidence parse· fetched 3 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Official advisory · high-confidence parse· fetched 3 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat

More Red Hat Linux advisories

All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Download on the App StoreGet CVE alerts on AndroidSee app features

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.