/

CVE-2026-33870

Severity:

HIGH RISK

(7.5)

HTTP Request Smuggling in Netty HTTP/1.1

CVE-2026-33870

Modified

Vulnerability type

Category:

HTTP Request Smuggling

CWE:

CWE-444

Impact:

Request Smuggling and Security Control Bypass

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Netty's HTTP/1.1 handling incorrectly parses quoted strings in chunked transfer encoding extension values in affected versions.

When front-end and back-end components disagree on how to interpret these extensions, an attacker can perform HTTP request smuggling, potentially bypassing security controls and confusing downstream services.

Affected context

This vulnerability appears in applications and services that:

  • Use Netty as the HTTP/1.1 server or client framework
  • Accept or forward HTTP requests using chunked transfer encoding
  • Sit behind or in front of other HTTP-aware components (e.g., reverse proxies, load balancers, API gateways, WAFs)

The issue is triggered when Netty's parsing of chunked transfer encoding extension values, especially with quoted strings, diverges from how other HTTP components in the chain parse the same data.

Exploit preconditions

  • Attack surface: HTTP/1.1 endpoints that accept chunked transfer encoding requests through Netty.
  • Required access: Ability to send crafted HTTP requests to an affected Netty-based service (typically unauthenticated network access to the HTTP interface).
  • Trigger point: Parsing of Transfer-Encoding: chunked requests that include carefully constructed chunk extensions with quoted strings.
  • Why exploitation is possible: Netty's parsing logic for chunked encoding extensions differs from that of other HTTP components in the request path, allowing an attacker to desynchronize their view of where one request ends and the next begins.

Why this happens

The root cause is an inconsistency in Netty's HTTP/1.1 chunked transfer encoding parser when handling quoted strings in chunk extension values.

According to HTTP specifications, intermediaries and servers must agree on how to interpret chunked messages, including any extension parameters.

Netty's parser treats certain quoted extension sequences differently than upstream or downstream components, leading to message boundary confusion.

This maps to CWE-444: Inconsistent Interpretation of HTTP Requests, where different implementations interpret the same HTTP stream in incompatible ways, enabling attackers to inject or smuggle additional requests through desynchronization rather than through syntactic violations alone.

Potential impact

  • Bypass of HTTP security controls such as WAFs, rate limiters, or authentication gateways.
  • Smuggling of hidden requests to backend services that the front-end proxy did not intend to forward.
  • Execution of actions as a different user context if smuggled requests are processed within an authenticated connection.
  • Cache poisoning or cache desynchronization on shared HTTP caches.
  • Abuse of internal-only endpoints that are expected to be unreachable from the public internet.

General mitigation guidance

Defensive strategies focus on enforcing consistent and conservative HTTP parsing across the request chain and minimizing trust in complex encodings:

  • Align HTTP parsing behavior between edge components (e.g., load balancers, reverse proxies) and Netty by adhering to strict, spec-compliant parsing rules for transfer encoding and extensions.
  • Normalize or strip non-essential chunked transfer encoding extensions at a trusted boundary, reducing ambiguity in how extensions are interpreted.
  • Prefer simpler and explicit request framing (e.g., Content-Length for known-size requests) where operationally viable, reducing exposure to chunked parsing edge cases.
  • Apply least-privilege design to backend endpoints so that even if a smuggled request reaches them, accessible functionality and data are tightly constrained.
  • Configure front-end infrastructure to reject or sanitize suspicious or malformed chunked requests, especially those with unusual extension syntax or quoting patterns.

How teams detect issues like this

Detection typically combines configuration review, code analysis, and runtime monitoring:

  • Use static analysis or code review to identify custom HTTP parsing, relaxed validation logic, or direct reliance on nuanced chunked extension semantics within Netty-based services.
  • Review reverse proxy and load balancer configurations to ensure consistent HTTP/1.1 parsing behavior and to identify permissive settings for chunked transfer encoding and extensions.
  • Employ security testing tools or dynamic scanners designed to probe for HTTP request smuggling by sending crafted chunked requests and analyzing backend behavior.
  • Monitor logs for anomalies such as mismatched request counts between front-end and back-end, unexpected 400/408/502 errors, or unexplained requests appearing on backend logs without corresponding entries at the edge.
  • Integrate automated HTTP hardening checks into CI/CD and deployment pipelines to flag risky parser configurations or non-standard behaviors.

Sources

SourceLink
github.comgithub.com/netty/netty/security/advisories/GHSA-pwqr-wmgm-9rr8
w4ke.infow4ke.info/2025/06/18/funky-chunks.html
w4ke.infow4ke.info/2025/10/29/funky-chunks-2.html
rfc-editor.orgrfc-editor.org/rfc/rfc9110
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10175
access.redhat.comaccess.redhat.com/errata/RHSA-2026:10184
access.redhat.comaccess.redhat.com/errata/RHSA-2026:13571
access.redhat.comaccess.redhat.com/errata/RHSA-2026:14272
access.redhat.comaccess.redhat.com/errata/RHSA-2026:14276
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17668
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17789
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18054
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18055
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18059
access.redhat.comaccess.redhat.com/errata/RHSA-2026:22619
access.redhat.comaccess.redhat.com/errata/RHSA-2026:34608
access.redhat.comaccess.redhat.com/errata/RHSA-2026:7109
access.redhat.comaccess.redhat.com/errata/RHSA-2026:7380
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8159
access.redhat.comaccess.redhat.com/errata/RHSA-2026:8509
access.redhat.comaccess.redhat.com/security/cve/CVE-2026-33870
bugzilla.redhat.combugzilla.redhat.com/show_bug.cgi?id=2452453
security.access.redhat.comsecurity.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33870.json

Frequently asked

questions

Exploitability depends on the overall HTTP architecture. It becomes most impactful when a Netty-based service sits behind or in front of other HTTP components that parse chunked transfer encoding differently, creating the conditions needed for request smuggling.

Typically no. In many deployments, the attacker only needs network access to the affected HTTP endpoint and the ability to send specially crafted chunked requests. Authentication may increase impact if smuggled requests reuse authenticated connections.

The safest pattern is to ensure strict, spec-compliant, and consistent HTTP parsing of chunked transfer encoding across all components. This includes adopting corrected parsing logic, normalizing or removing complex chunk extensions, and enforcing conservative behavior when ambiguities are detected.

Future designs should minimize reliance on complex or rarely used HTTP features, enforce uniform parsing behavior across the entire request path, and subject HTTP parsing logic and configuration to focused security review and automated testing for desynchronization and request smuggling scenarios.

Find out what's already
exploitable in your codebase.