limbo.watch

In limbo for 63 days

GHSA-2g6j-r8q9-5hr8

io.netty:netty-codec-http on Maven · published in netty/netty

Read the advisory on GitHub ↗

Fixed in 4.2.17.Final. Dependabot, npm audit and OSV-Scanner won’t flag this yet. Find it in your project

Facts

Severity
High · CVSS score 7.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Affected versions (io.netty:netty-codec-http)
>=4.2.0.Final,<=4.2.16.FinalAs entered by the maintainer. Not reviewed.
Fixed in (io.netty:netty-codec-http)
4.2.17.Final
Affected versions (io.netty:netty-codec-http)
<=4.1.136.FinalAs entered by the maintainer. Not reviewed.
Fixed in (io.netty:netty-codec-http)
4.1.137.Final
CVE
None cited by the advisory
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
CVE-2026-100666 (published by another CNA)

If you use io.netty:netty-codec-http >=4.2.0.Final,<=4.2.16.Final

Upgrade to 4.2.17.Final or later. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2026-09-10 14:07 UTC

    Published by the maintainers

    No CVE cited

  2. 2026-10-28 07:45 UTC

    First seen by Limbowatch

    not reviewed · not in OSV

  3. Waiting

    Reviewed by GitHub

  4. Waiting

    In OSV; scanners can see it

Machine-readable record: feed/GHSA-2g6j-r8q9-5hr8.json