Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

HTTP Request Smuggling in Netty

CVE-2019-16869GHSA-p979-4mfw-53vg

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven io.netty:netty-all

    Affected
    >= 4.0.0.Beta1, < 4.1.42.Final
    Fixed in
    4.1.42.Final

  • Maven io.netty:netty

    Affected
    >= 3.3.0.Final, <= 4.0.0.Alpha8
    Fixed in
    no fixed version recorded

  • Maven org.jboss.netty:netty

    Affected
    <= 3.2.9.Final
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
  • CVE-2019-16869: 8.64% estimated exploitation activity in the next 30 days; percentile 95.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Netty before 4.1.42.Final mishandles whitespace before the colon in HTTP headers (such as a "Transfer-Encoding : chunked" line), which leads to HTTP request smuggling.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-p979-4mfw-53vg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-16869

Advisory: HTTP Request Smuggling in Netty
IDs: CVE-2019-16869, GHSA-p979-4mfw-53vg
Record: https://patchnext.com/advisories/cve-2019-16869 (revision 1, source checked 26 Oct 2026, 16:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: io.netty:netty-all 4.1.42.Final. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.netty:netty-all: affected >= 4.0.0.Beta1, < 4.1.42.Final; fixed in 4.1.42.Final
- Maven io.netty:netty: affected >= 3.3.0.Final, <= 4.0.0.Alpha8
- Maven org.jboss.netty:netty: affected <= 3.2.9.Final

## Suggested inspection (read-only)
- Maven io.netty:netty-all: check the installed version with your package manager.
- Maven io.netty:netty: check the installed version with your package manager.
- Maven org.jboss.netty:netty: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.netty:netty-all, io.netty:netty, org.jboss.netty:netty.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p979-4mfw-53vg (GitHub-reviewed advisory GHSA-p979-4mfw-53vg lists affected ranges: Maven io.netty:netty-all >=4.0.0.Beta1 =0 =3.3.0.Final <=4.0.0.Alpha8)

Commands are suggestions: review each one before running it.

Loading voting…