CLSA-2026-1793710149: TuxCare security update for io.netty (12 CVEs)

Published Nov 3, 2026
ยท
Updated

TuxCare rebuilt 36 io.netty packages to address 12 CVEs. Fixed in 4.1.29.Final-tuxcare.3.

Affected Software

36 affected componentsFixes available
tuxcare/io.netty:netty-all>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-bom>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-buffer>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-dns>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-haproxy>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-http>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-http2>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-memcache>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-mqtt>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-redis>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-smtp>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-socks>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-stomp>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-codec-xml>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-common>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-dev-tools>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-example>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-handler>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-handler-proxy>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-microbench>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-parent>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-resolver>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-resolver-dns>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-testsuite>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-testsuite-autobahn>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-testsuite-http2>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-testsuite-osgi>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-transport>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-transport-native-epoll>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-transport-native-kqueue>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-transport-native-unix-common>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-transport-native-unix-common-tests>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-transport-rxtx>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-transport-sctp>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3
tuxcare/io.netty:netty-transport-udt>=4.1.29.Final<4.1.29.Final-tuxcare.3
4.1.29.Final-tuxcare.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade tuxcare/io.netty:netty-all to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  2. Upgrade

    Upgrade tuxcare/io.netty:netty-bom to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  3. Upgrade

    Upgrade tuxcare/io.netty:netty-buffer to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  4. Upgrade

    Upgrade tuxcare/io.netty:netty-codec to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  5. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-dns to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  6. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-haproxy to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  7. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-http to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  8. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-http2 to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  9. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-memcache to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  10. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-mqtt to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  11. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-redis to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  12. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-smtp to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  13. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-socks to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  14. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-stomp to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  15. Upgrade

    Upgrade tuxcare/io.netty:netty-codec-xml to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  16. Upgrade

    Upgrade tuxcare/io.netty:netty-common to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  17. Upgrade

    Upgrade tuxcare/io.netty:netty-dev-tools to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  18. Upgrade

    Upgrade tuxcare/io.netty:netty-example to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  19. Upgrade

    Upgrade tuxcare/io.netty:netty-handler to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  20. Upgrade

    Upgrade tuxcare/io.netty:netty-handler-proxy to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  21. Upgrade

    Upgrade tuxcare/io.netty:netty-microbench to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  22. Upgrade

    Upgrade tuxcare/io.netty:netty-parent to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  23. Upgrade

    Upgrade tuxcare/io.netty:netty-resolver to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  24. Upgrade

    Upgrade tuxcare/io.netty:netty-resolver-dns to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  25. Upgrade

    Upgrade tuxcare/io.netty:netty-testsuite to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  26. Upgrade

    Upgrade tuxcare/io.netty:netty-testsuite-autobahn to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  27. Upgrade

    Upgrade tuxcare/io.netty:netty-testsuite-http2 to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  28. Upgrade

    Upgrade tuxcare/io.netty:netty-testsuite-osgi to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  29. Upgrade

    Upgrade tuxcare/io.netty:netty-transport to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  30. Upgrade

    Upgrade tuxcare/io.netty:netty-transport-native-epoll to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  31. Upgrade

    Upgrade tuxcare/io.netty:netty-transport-native-kqueue to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  32. Upgrade

    Upgrade tuxcare/io.netty:netty-transport-native-unix-common to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  33. Upgrade

    Upgrade tuxcare/io.netty:netty-transport-native-unix-common-tests to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  34. Upgrade

    Upgrade tuxcare/io.netty:netty-transport-rxtx to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  35. Upgrade

    Upgrade tuxcare/io.netty:netty-transport-sctp to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  36. Upgrade

    Upgrade tuxcare/io.netty:netty-transport-udt to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3
  37. Upgrade

    Upgrade io.netty to a version that resolves this vulnerability.

    Fixed in 4.1.29.Final-tuxcare.3

Event History

Nov 3, 2026
Advisory Published
via OSVยท01:49 PM
Data Sourced
via OSVยท01:49 PM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which package version contains the fixes?

The 12 CVEs are fixed in io.netty version 4.1.29.Final-tuxcare.3.

2

Which io.netty components are identified as affected by this update?

The advisory identifies netty-all, netty-bom, netty-buffer, netty-codec, netty-codec-dns, netty-codec-haproxy, netty-codec-http, and netty-codec-http2. It states that 36 io.netty packages were rebuilt.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
ยฉ 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203