CVE-2026-41417

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
22.5%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 11, 2026

Advisory Details (1)

Auto-updated May 11, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Start-Line Injection in DefaultHttpRequest.setUri() Allows HTTP Request Smuggling and RTSP Request Injection · Advisory · netty/netty · GitHub

https://github.com/netty/netty/security/advisories/GHSA-v8h7-rr48-vmmv

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.netty:netty-codec-http4.2.0.Alpha1 ... 4.2.9.Final (23 versions)4.2.13.Final—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-26 23:05 UTCEG score recompute
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-24 14:05 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 61 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-19 19:25 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-17 17:53 UTCEPSS rescore
  6. 2026-06-16 17:52 UTCEPSS rescore
  7. 2026-06-15 17:49 UTCEPSS rescore
  8. 2026-06-14 07:12 UTCEG score recompute
  9. 2026-06-13 23:00 UTCEPSS rescore
  10. 2026-06-12 23:12 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-06-12 02:53 UTCEG score recompute
  13. 2026-06-11 14:00 UTCEPSS rescore
  14. 2026-06-11 01:16 UTCEG score recompute
  15. 2026-06-10 22:18 UTCEPSS rescore
  16. 2026-06-10 13:22 UTCEPSS rescore
  17. 2026-06-10 13:22 UTCEPSS rescore
  18. 2026-06-09 23:39 UTCEG score recompute
  19. 2026-06-08 22:02 UTCEG score recompute
  20. 2026-06-08 14:17 UTCEPSS rescore
  21. 2026-06-08 14:17 UTCEPSS rescore
  22. 2026-06-07 18:58 UTCEG score recompute
  23. 2026-06-07 15:25 UTCEPSS rescore
  24. 2026-06-07 15:25 UTCEPSS rescore
  25. 2026-06-06 17:20 UTCEG score recompute
  26. 2026-06-06 13:47 UTCEPSS rescore
  27. 2026-06-06 13:47 UTCEPSS rescore
  28. 2026-06-05 22:47 UTCEPSS rescore
  29. 2026-06-05 15:43 UTCEG score recompute
  30. 2026-06-04 14:06 UTCEG score recompute
  31. 2026-06-04 13:12 UTCEPSS rescore
  32. 2026-06-04 13:12 UTCEPSS rescore
  33. 2026-06-03 12:29 UTCEG score recompute
  34. 2026-06-02 20:13 UTCEPSS rescore
  35. 2026-06-02 10:52 UTCEG score recompute
  36. 2026-06-01 13:52 UTCEPSS rescore
  37. 2026-06-01 13:52 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-06-01 09:15 UTCEG score recompute
  40. 2026-05-31 22:30 UTCEPSS rescore
  41. 2026-05-31 22:30 UTCEPSS rescore
  42. 2026-05-31 00:16 UTCEPSS rescore
  43. 2026-05-31 00:16 UTCEPSS rescore
  44. 2026-05-31 00:16 UTCEPSS rescore
  45. 2026-05-29 13:44 UTCEPSS rescore
  46. 2026-05-29 13:44 UTCEPSS rescore
  47. 2026-05-28 13:44 UTCEPSS rescore
  48. 2026-05-28 13:44 UTCEPSS rescore
  49. 2026-05-28 13:44 UTCEPSS rescore
  50. 2026-05-27 13:40 UTCEPSS rescore
  51. 2026-05-27 13:40 UTCEPSS rescore
  52. 2026-05-27 13:40 UTCEPSS rescore
  53. 2026-05-26 13:44 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-26 07:18 UTCEPSS rescore
  56. 2026-05-23 00:08 UTCEG score recompute
  57. 2026-05-20 22:38 UTCEPSS rescore
  58. 2026-05-20 22:38 UTCEPSS rescore
  59. 2026-05-20 14:00 UTCEG score recompute
  60. 2026-05-20 11:22 UTCEPSS rescore
  61. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-41417?
CVE-2026-41417 is a medium vulnerability published on May 6, 2026. 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…
When was CVE-2026-41417 disclosed?
CVE-2026-41417 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41417 actively exploited?
CVE-2026-41417 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41417?
CVE-2026-41417 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-41417?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41417, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41417

Explore →

Is Your Infrastructure Affected by CVE-2026-41417?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs