Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-84h7-rjj3-6jx4

Netty has a CRLF Injection vulnerability in io.netty.handler.codec.http.HttpRequestEncoder

CVSS 6.5 MediumEPSS 0.0032 · 25th percentile

Published by the GitHub Advisory Database at 15 Dec 2025, 23:28 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.netty:netty-codec-httpMaven>=4.2.0.Alpha1, <4.2.8.Final || <4.1.129.Final4.2.8.Final, 4.1.129.Final
Identifiers
GHSA-84h7-rjj3-6jx4 · CVE-2025-67735
Weakness (CWE)
CWE-93
Tags
Published
15 Dec 2025
Updated
10 Sept 2026

Machine-written summary

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

Netty's io.netty:netty-codec-http package is affected from 4.2.0.Alpha1 before 4.2.8.Final, and from 4.1.129.Final before... (affected range as listed: versions below 4.2.8.Final and below 4.1.129.Final). The HttpRequestEncoder does not sanitize the request URI, so CRLF characters in it can be injected into the request line. An application that passes untrusted input into the URI and uses this encoder can have requests smuggled. Upgrade to netty-codec-http 4.2.8.Final or 4.1.129.Final. The source gives few details on the exact preconditions.

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
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0032, the 25th percentile, on 12 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.