Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV

CVE-2026-42578 netty-handler-proxy

CVE-2026-42578 is a CWE-113 vulnerability in io.netty:netty-handler-proxy. A fix is available for io.netty:netty-handler-proxy — see the affected versions and patch details below.

Netty: HTTP Header Injection via HttpProxyHandler Disabled Validation

Also known asGHSA-45q3-82m4-75jr
Published
May 13, 2026
Updated
Sep 20, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-42578.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected
io.netty:netty-handler-proxyio.netty:netty-handler-proxy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, Netty's HttpProxyHandler constructs HTTP CONNECT requests with header validation explicitly disabled. The newInitialMessage() method creates headers using DefaultHttpHeadersFactory.headersFactory().withValidation(false), then adds user-provided outboundHeaders without any CRLF validation. This allows an attacker who can influence the outbound headers to inject arbitrary HTTP headers into the CONNECT request sent to the proxy server. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.netty:netty-handler-proxyall versions4.1.133.Finalio.netty:netty-handler-proxy:4.1.133.Final
Mavenio.netty:netty-handler-proxy4.2.0.Alpha1&&< 4.2.13.Final4.2.13.Finalio.netty:netty-handler-proxy:4.2.13.Final

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.netty:netty-handler-proxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.netty:netty-handler-proxy to 4.1.133.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42578 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-42578 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-42578. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Important: This vulnerability in Netty's HttpProxyHandler allows for HTTP header injection into CONNECT requests when an attacker can influence outbound headers. The handler's explicit disabling of header validation could enable proxy-related attacks, such as cache poisoning or bypassing security controls, impacting…

ProductFixed inAdvisory
Cryostat 4 on RHEL 9cryostat/cryostat-reports-rhel9:4.2.0-10RHSA-2026:28010
Red Hat AMQ Broker 7.13.6netty-handler-proxyRHSA-2026:66545
Red Hat AMQ Broker 7.14.1netty-handler-proxyRHSA-2026:66488
Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16netty-handler-proxyRHSA-2026:37390
Red Hat build of Quarkus 3.27.4netty-handler-proxyRHSA-2026:23808
Red Hat build of Quarkus 3.33.2see advisoryRHSA-2026:24502
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el7eapRHSA-2026:53644
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el8eapRHSA-2026:53645

Frequently Asked Questions

Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, Netty's HttpProxyHandler constructs HTTP CONNECT requests with header validation explicitly disabled. The newInitialMessage() method creates headers using DefaultHttpHeadersFactory.headersFactory().withValidation(false), then adds user-provided outboundHeaders without any CRLF validation. This allows an attacker who can influence the outbound headers to inject arbitrary HTTP headers into the CONNECT request sent to the proxy server. This vulnerability is fixed in 4.2.13.Final and 4.1.
O3 Security · Impact-Aware SCA

Is CVE-2026-42578 in your dependencies?

O3 Security finds CVE-2026-42578 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2026-42578: netty-handler-proxy | O3 Security