p PatchFirst

CVE-2026-100659

CVE-2026-100659 · Netty 4.2.0 through 4.2.17 HTTP/3 Request Routing Bypass

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Netty's HTTP/3 codec (io.netty:netty-codec-http3) in versions 4.2.0.Final through 4.2.17.Final does not enforce the RFC 9114 requirement that the :authority pseudo-header field and a literal host header field, when both present, carry the same value. A remote unauthenticated peer can send a single HEADERS frame containing both fields with differing, attacker-controlled values; the request is accepted and delivered to the application with two conflicting authorities, allowing routing, virtual-host, and access-control decisions to be bypassed when different components in the request path consult different fields. This issue is fixed in 4.2.18.Final.

CVSS 6.9 · Medium · EPSS 0.2% · Fix available

Published
Updated

Stack: system

Affected products and versions

  • netty

    Versions
    • ≥ 4.2.0.Final, < 4.2.18.Final: Affected (custom)
    • 4.2.18.Final: Not affected (custom)

    Update to 4.2.18.Final

  • netty Ubuntu:Pro:14.04:LTS

    Versions
    • 1:3.2.6.Final-2
    • 1:3.2.6.Final-2+deb8u2build0.14.04.1~esm1
    • 1:3.2.6.Final-2+deb8u2ubuntu0.1~esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • netty Ubuntu:Pro:16.04:LTS

    Versions
    • 1:3.2.6.Final-2
    • 1:4.0.32-1
    • 1:4.0.33-1
    • 1:4.0.34-1
    • 1:4.0.34-1ubuntu0.1~esm1
    • 1:4.0.34-1ubuntu0.1~esm2
    • 1:4.0.34-1ubuntu0.1~esm3
    • 1:4.0.34-1ubuntu0.1~esm4
    • 1:4.0.34-1ubuntu0.1~esm5
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • netty Ubuntu:Pro:18.04:LTS

    Versions
    • 1:4.1.7-4
    • 1:4.1.7-4ubuntu0.1~esm1
    • 1:4.1.7-4ubuntu0.1
    • 1:4.1.7-4ubuntu0.1+esm1
    • 1:4.1.7-4ubuntu0.1+esm2
    • 1:4.1.7-4ubuntu0.1+esm3
    • 1:4.1.7-4ubuntu0.1+esm4
    • 1:4.1.7-4ubuntu0.1+esm5
    • 1:4.1.7-4ubuntu0.1+esm6
    • 1:4.1.7-4ubuntu0.1+esm7
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • netty Ubuntu:Pro:20.04:LTS

    Versions
    • 1:4.1.33-1
    • 1:4.1.33-2
    • 1:4.1.33-3
    • 1:4.1.45-1
    • 1:4.1.45-1ubuntu0.1~esm1
    • 1:4.1.45-1ubuntu0.1~esm2
    • 1:4.1.45-1ubuntu0.1~esm3
    • 1:4.1.45-1ubuntu0.1~esm4
    • 1:4.1.45-1ubuntu0.1~esm6
    • 1:4.1.45-1ubuntu0.1~esm7
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • netty Ubuntu:Pro:22.04:LTS

    Versions
    • 1:4.1.48-4
    • 1:4.1.48-4+deb11u1build0.22.04.1
    • 1:4.1.48-4+deb11u2build0.22.04.1
    • 1:4.1.48-4+deb11u2ubuntu0.1~esm1
    • 1:4.1.48-4+deb11u2ubuntu0.1~esm2
    • 1:4.1.48-4+deb11u2ubuntu0.1
    • 1:4.1.48-4+deb11u2ubuntu0.1+esm1
    • 1:4.1.48-4+deb11u2ubuntu0.1+esm3
    • 1:4.1.48-4+deb11u2ubuntu0.2
    • 1:4.1.48-4+deb11u2ubuntu0.2+esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • netty Ubuntu:Pro:24.04:LTS

    Versions
    • 1:4.1.48-7
    • 1:4.1.48-8
    • 1:4.1.48-9
    • 1:4.1.48-9ubuntu0.1~esm1
    • 1:4.1.48-9ubuntu0.1~esm2
    • 1:4.1.48-9ubuntu0.1
    • 1:4.1.48-9ubuntu0.1+esm1
    • 1:4.1.48-9ubuntu0.1+esm3
    • 1:4.1.48-9ubuntu0.2
    • 1:4.1.48-9ubuntu0.2+esm1
    • 1:4.1.48-9ubuntu0.2+esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • netty Ubuntu:26.10

    Versions
    • 1:4.1.48-16
    • 1:4.1.48-16ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • netty Ubuntu:Pro:26.04:LTS

    Versions
    • 1:4.1.48-10
    • 1:4.1.48-11
    • 1:4.1.48-12
    • 1:4.1.48-13
    • 1:4.1.48-14
    • 1:4.1.48-16
    • 1:4.1.48-16ubuntu0.1~esm2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →