CVE-2026-42009: Gnutls: gnutls: denial of service via dtls packet reordering vulnerability
A flaw was found in gnutls. A remote attacker could exploit an issue in the Datagram Transport Layer Security (DTLS) packet reordering logic. The comparator function, responsible for ordering DTLS packets by sequence numbers, did not correctly handle packets with duplicate sequence numbers. This could lead to unstable packet ordering or undefined behavior, resulting in a denial of service.
Security readout for executives and security teams
Plain-English summary
CVE-2026-42009 is a remotely reachable denial-of-service flaw in GnuTLS DTLS packet handling. An unauthenticated attacker may be able to disrupt affected services by triggering unstable packet ordering. The impact is availability only, but the affected Red Hat footprint is broad across RHEL 7 ELS, 8, 9, and 10 streams.
Executive priority
Treat as a high-priority availability risk, not a data-theft issue. Patch affected Red Hat systems on normal emergency or accelerated maintenance timelines, starting with externally reachable DTLS-dependent services and systems supporting critical business processes.
Technical view
The flaw is in GnuTLS DTLS packet reordering logic. A comparator used to order DTLS packets by sequence number mishandles duplicate sequence numbers, causing unstable ordering or undefined behavior and possible denial of service. CVSS 3.1 is 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
Likely exposure
Exposure is most likely on Red Hat systems running affected gnutls packages, especially where applications use DTLS over reachable network paths. The bundle lists affected RHEL 10, 10.0 EUS, 9, 9.4 SAP, 8, 8.4, 8.6, 8.8 SAP/TUS, and 7 ELS package streams.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The vulnerability is still operationally important because it is network reachable, requires no authentication or user interaction, and targets availability of services using affected DTLS handling.
Researcher notes
The provided evidence identifies duplicate DTLS sequence numbers as the logic edge case and CWE-475 as the weakness. It does not provide proof-of-concept details, exploit telemetry, or fixed version mapping beyond Red Hat advisory references, so validation should stay package- and service-inventory focused.
Mitigation direction
Apply the relevant Red Hat security advisory updates for affected systems.
Check Red Hat guidance for exact fixed package versions in each supported stream.
Prioritize internet-facing or partner-facing services that use DTLS via GnuTLS.
Reduce untrusted DTLS exposure where patching cannot happen immediately.
Monitor affected services for crashes, restarts, or availability degradation.
Validation and detection
Inventory installed gnutls and listed libtasn1 package versions on Red Hat hosts.
Map applications linked to GnuTLS and confirm whether they use DTLS.
Verify the applicable RHSA has been installed for each RHEL stream.
Confirm exposed DTLS services are patched or temporarily access-restricted.
Review service logs and monitoring for denial-of-service symptoms.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-475: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.