Vulnerability/
REDHAT-BUG-2456338

REDHAT-BUG-2456338

Published Apr 8, 2026

Updated

If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection can deadlock, causing uncontrolled consumption of resources. This can lead to a denial of service. This only affects TLS 1.3.

Affected Software

1 affected component

IETF TLS=1.3

Event History

Apr 8, 2026

Data Sourced

via Red Hat·02:01 AM

DescriptionSeverityAffected Software

Frequently Asked Questions

What is the severity of REDHAT-BUG-2456338?

The severity of REDHAT-BUG-2456338 is categorized as high due to its potential for causing denial of service.

How do I fix REDHAT-BUG-2456338?

To address REDHAT-BUG-2456338, you should update to the latest version of the affected software that corrects the issue.

Which versions of TLS are affected by REDHAT-BUG-2456338?

REDHAT-BUG-2456338 specifically affects TLS version 1.3.

What are the potential impacts of REDHAT-BUG-2456338?

The potential impact of REDHAT-BUG-2456338 includes deadlocking of the TLS connection and subsequent uncontrolled resource consumption.

Is it safe to use TLS 1.3 after REDHAT-BUG-2456338?

Using TLS 1.3 is not safe after REDHAT-BUG-2456338 unless appropriate patches and updates have been applied.

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.