CVE intelligence and bounded remediation

CVE-2026-41417 — Netty Netty security vulnerability

Medium CVSS 5.3

Netty allows request-line validation to be bypassed when a `DefaultHttpRequest` or `DefaultFullHttpRequest` is created first and its URI is later changed via `setUri()`. The constructors reject CRLF and whitespace characters that would break the start-line, but `setUri()` does not apply the same validation. `HttpRequestEncoder` and `RtspEncoder` then write the URI into the request line verbatim. If attacker-controlled input reaches `setUri()`, this enables CRLF injection and insertion of additional HTTP or RTSP requests, leading to HTTP request smuggling or desynchronization on the HTTP side and request injection on the RTSP side. This issue is fixed in versions 4.2.13.Final and 4.1.133.Final.

Severity
Medium
CVSS
5.3 (3.1)
Published
2026-05-06
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-93, CWE-444

Affected products

  • netty / netty

Showing 1 representative product identities from 2 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

HTTP request smuggling and message-boundary ambiguity

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory every proxy, CDN, gateway, load balancer, service mesh, and application server hop on affected request paths.
  • Compare documented parsing and normalization behavior for message length, transfer coding, duplicate headers, and protocol translation.
  • Identify connection reuse and which downstream services trust headers added by intermediaries.

Remediate safely

  • Update affected intermediaries and origin servers and align them on a single standards-compliant request framing policy.
  • Reject ambiguous length, transfer-coding, duplicate, malformed, and unsupported framing before forwarding.
  • Normalize or remove hop-by-hop and identity headers at one controlled boundary and add multi-hop regression tests.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.