Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

Loop with Unreachable Exit Condition in Netty

CVE-2016-4970GHSA-rv63-gqm8-9w8q

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (io.netty:netty-handler 4.1.1.Final, 4.0.37.Final), redeploy, then verify what is actually installed.

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-handler

    Affected
    >= 4.0.0.Alpha1, < 4.0.37.Final>= 4.1.0.Beta1, < 4.1.1.Final
    Fixed in
    4.0.37.Final, 4.1.1.Final

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:N/A:H
EPSS
  • CVE-2016-4970: 11.26% estimated exploitation activity in the next 30 days; percentile 95.97 (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.

handler/ssl/OpenSslEngine.java in Netty 4.0.x before 4.0.37.Final and 4.1.x before 4.1.1.Final allows remote attackers to cause a denial of service (infinite loop).

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

    Published from ghsa record GHSA-rv63-gqm8-9w8q

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-2016-4970

Advisory: Loop with Unreachable Exit Condition in Netty
IDs: CVE-2016-4970, GHSA-rv63-gqm8-9w8q
Record: https://patchnext.com/advisories/cve-2016-4970 (revision 1, source checked 26 Oct 2026, 16:16 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: Vendor fix available; fixed versions by package: io.netty:netty-handler 4.1.1.Final, 4.0.37.Final. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.netty:netty-handler: affected >= 4.0.0.Alpha1, < 4.0.37.Final; >= 4.1.0.Beta1, < 4.1.1.Final; fixed in 4.0.37.Final, 4.1.1.Final

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.netty:netty-handler.
- 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-rv63-gqm8-9w8q (GitHub-reviewed advisory GHSA-rv63-gqm8-9w8q lists affected ranges: Maven io.netty:netty-handler >=4.0.0.Alpha1 =4.1.0.Beta1 <4.1.1.Final)

Commands are suggestions: review each one before running it.

Loading voting…