Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-v8h7-rr48-vmmv

Netty: Start-Line Injection in DefaultHttpRequest.setUri() Allows HTTP Request Smuggling and RTSP Request Injection

CVSS 5.3 MediumEPSS 0.0032 · 24th percentile

Published by the GitHub Advisory Database at 5 May 2026, 18:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.netty:netty-codec-httpMaven<4.1.133.Final || >=4.2.0.Alpha1, <4.2.13.Final4.1.133.Final, 4.2.13.Final
Identifiers
GHSA-v8h7-rr48-vmmv · CVE-2026-41417
Weakness (CWE)
CWE-93 · CWE-444
Tags
Published
5 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Netty's netty-codec-http package, versions before 4.1.133.Final and from 4.2.0.Alpha1 before 4.2.13.Final, does not validate the request URI when it is changed with setUri() on DefaultHttpRequest or DefaultFullHttpRequest, though the constructors do. An attacker who can influence the value passed to setUri() can inject CRLF sequences, enabling HTTP request smuggling or RTSP request injection when the request is encoded. Upgrade to 4.1.133.Final or 4.2.13.Final, and avoid passing untrusted input to setUri().

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0032, the 24th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.