MediumGHSA-8c42-7qj2-3j46CVE-2026-59903

Netty Vulnerable to Cache Poisoning and Information Disclosure via CORS Vary Header Overwrite

Published 17 Aug 2026 · Updated 10 Sept 2026

Is your project on an affected io.netty:netty-codec-http?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=4.2.0.Final <4.2.17.Final
Fixed in
4.2.17.Final
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.netty:netty-codec-http -DdepVersion=4.2.17.Final -DforceVersion=true
Affected
<4.1.137.Final
Fixed in
4.1.137.Final
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.netty:netty-codec-http -DdepVersion=4.1.137.Final -DforceVersion=true

Details

Summary

Netty's CorsHandler silently overwrites existing Vary headers, enabling cache poisoning and sensitive information disclosure.

Details

io.netty.handler.codec.http.cors.CorsHandler#setVaryHeader overwrites any existing Vary headers set by backend applications.

    private static void setVaryHeader(final HttpResponse response) {
        response.headers().set(HttpHeaderNames.VARY, HttpHeaderNames.ORIGIN);
    }

Because set() replaces all existing values for the header, if a backend application sets a Vary header (such as Vary: Authorization or Vary: Cookie) to ensure that intermediate caches (like CDNs) cache responses separately per user, the CorsHandler will overwrite it with Vary: origin. This causes the caching proxy to ignore the authorization context and cache the response based solely on the URL and Origin, allowing an attacker to retrieve another user's cached sensitive data.

Impact

This is a Cache Poisoning vulnerability that leads to Information Disclosure. It impacts any Netty-based web application that uses the CorsHandler, sets its own Vary headers to manage caching of authenticated or user-specific responses (e.g., Vary: Authorization), and is deployed behind a caching proxy or CDN. The end-users of these applications are impacted, as their sensitive data may be leaked to unauthorized actors.

Is GHSA-8c42-7qj2-3j46 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected io.netty:netty-codec-http, and gives you the command that fixes it.

More advisories for io.netty:netty-codec-http

  • MediumCVE-2026-59921Netty: CRLF Injection via Multipart Filename in Netty HttpPostRequestEncoder · 22 Jul 2026
  • MediumCVE-2026-59899Netty: [HttpContentEncoder] Unbounded Per-Connection Queue Growth via HTTP/1.1 Pipelining Leads to Denial of Service · 22 Jul 2026
  • MediumCVE-2026-59898Netty: WebSockets V07/V08 handshaker missing Connection/Upgrade validation · 22 Jul 2026
  • MediumCVE-2026-56746Netty: Security Control Bypass via CORS Short-Circuit Failure · 22 Jul 2026
  • HighCVE-2026-56745Netty: [SpdyHttpDecoder] ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion · 22 Jul 2026
  • HighCVE-2026-55833Netty SPDY zlib header block continues decoded expansion after maxHeaderSize truncation · 22 Jul 2026
All 24 advisories for io.netty:netty-codec-http

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.