CVE-2026-42009: gnutls: DTLS packet-reorder bug DoS hits AI inference servers
HIGHA flaw in gnutls' DTLS packet-reordering comparator fails to handle duplicate sequence numbers, leading to unstable ordering or undefined behavior that a remote, unauthenticated attacker can trigger over the network to cause a denial of service (CVSS 7.5, AV:N/AC:L/PR:N/UI:N). This isn't an AI-specific attack technique, but it lands squarely on AI infrastructure: Red Hat's AI Inference Server images (rhaiis/vllm-rocm-rhel9, rhaiis/model-opt-cuda-rhel9) bundle the vulnerable library, and gnutls itself has 129 downstream dependents and a package risk score of 61/100 with 82 other CVEs on record. The EPSS score of 1.3% (top 32nd percentile) is modest, there's no CISA KEV listing, no public exploit, and no Nuclei template, so urgency is moderate rather than critical. Patch via the relevant RHSA errata (RHSA-2026:13274 and related builds) to update gnutls/libtasn1 across affected images, prioritizing any inference-serving hosts that terminate DTLS, and monitor for unexpected crash-restart patterns on DTLS-facing services as a detection signal in the interim.
What is the risk?
CVSS 7.5 (high) reflects a network-exploitable, unauthenticated, low-complexity DoS with no user interaction required — a favorable exploit profile on paper. However, real-world exploitation likelihood is tempered: EPSS sits at just 1.3% (top 32% percentile, not top-tier), there is no CISA KEV entry, no public exploit code, and no Nuclei scanner template, indicating this has not attracted active attacker interest. The residual risk driver is exposure and blast radius rather than active exploitation: gnutls is a foundational TLS/DTLS library with 129 downstream dependents and a history of 82 other CVEs (package risk score 61/100), and it ships inside Red Hat's AI Inference Server container images, meaning any DTLS-terminating AI inference deployment inherits this exposure until patched.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| vLLM | pip | — | No patch |
| discovery/discovery-server-rhel9 | — | — | No patch |
| discovery/discovery-ui-rhel9 | — | — | No patch |
| gnutls | — | — | No patch |
| gnutls-main | — | — | No patch |
| libtasn1 | — | — | No patch |
| rhaiis/model-opt-cuda-rhel9 | — | — | No patch |
| rhcos | — | — | No patch |
| rhui5/cds-rhel9 | — | — | No patch |
| rhui5/haproxy-rhel9 | — | — | No patch |
| rhui5/installer-rhel9 | — | — | No patch |
| rhui5/rhua-rhel9 | — | — | No patch |
How severe is it?
What is the attack surface?
What should I do?
1 step-
Patch gnutls and libtasn1 to the fixed versions referenced in the Red Hat errata (RHSA-2026:13274, 20611-20613, 26319, 26409, 29197, 29794, 30004, 30849) across all affected products, prioritizing rhaiis inference-server images and rhcos hosts. Rebuild and redeploy affected container images (rhaiis/vllm-rocm-rhel9, rhaiis/model-opt-cuda-rhel9) rather than patching in place. If immediate patching isn't feasible, restrict network exposure of DTLS-terminating services via firewall/network policy and disable DTLS where not strictly required. For detection, monitor for abnormal crash-restart loops or service interruptions on DTLS-facing endpoints, and inspect traffic for repeated packets carrying duplicate DTLS sequence numbers as a leading indicator of exploitation attempts.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-42009?
A flaw in gnutls' DTLS packet-reordering comparator fails to handle duplicate sequence numbers, leading to unstable ordering or undefined behavior that a remote, unauthenticated attacker can trigger over the network to cause a denial of service (CVSS 7.5, AV:N/AC:L/PR:N/UI:N). This isn't an AI-specific attack technique, but it lands squarely on AI infrastructure: Red Hat's AI Inference Server images (rhaiis/vllm-rocm-rhel9, rhaiis/model-opt-cuda-rhel9) bundle the vulnerable library, and gnutls itself has 129 downstream dependents and a package risk score of 61/100 with 82 other CVEs on record. The EPSS score of 1.3% (top 32nd percentile) is modest, there's no CISA KEV listing, no public exploit, and no Nuclei template, so urgency is moderate rather than critical. Patch via the relevant RHSA errata (RHSA-2026:13274 and related builds) to update gnutls/libtasn1 across affected images, prioritizing any inference-serving hosts that terminate DTLS, and monitor for unexpected crash-restart patterns on DTLS-facing services as a detection signal in the interim.
Is CVE-2026-42009 actively exploited?
No confirmed active exploitation of CVE-2026-42009 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-42009?
Patch gnutls and libtasn1 to the fixed versions referenced in the Red Hat errata (RHSA-2026:13274, 20611-20613, 26319, 26409, 29197, 29794, 30004, 30849) across all affected products, prioritizing rhaiis inference-server images and rhcos hosts. Rebuild and redeploy affected container images (rhaiis/vllm-rocm-rhel9, rhaiis/model-opt-cuda-rhel9) rather than patching in place. If immediate patching isn't feasible, restrict network exposure of DTLS-terminating services via firewall/network policy and disable DTLS where not strictly required. For detection, monitor for abnormal crash-restart loops or service interruptions on DTLS-facing endpoints, and inspect traffic for repeated packets carrying duplicate DTLS sequence numbers as a leading indicator of exploitation attempts.
What systems are affected by CVE-2026-42009?
This vulnerability affects the following AI/ML architecture patterns: model serving, network/transport layer (DTLS), AI inference infrastructure.
What is the CVSS score for CVE-2026-42009?
CVE-2026-42009 has a CVSS v3.1 base score of 7.5 (HIGH). The EPSS exploitation probability is 1.33%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0029 Denial of AI Service AML.T0049 Exploit Public-Facing Application Compliance Controls Affected
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An attacker with network access to a DTLS-terminating endpoint on an AI inference deployment (for example, a control-plane or telemetry channel on a Red Hat AI Inference Server host) sends a stream of crafted DTLS packets containing duplicate sequence numbers. The vulnerable comparator in the packet-reordering logic mishandles these duplicates, producing unstable ordering or undefined behavior in the gnutls library, which crashes or hangs the process handling the connection — interrupting availability of the inference service until it is restarted or recovered.
Weaknesses (CWE)
CWE-475 — Undefined Behavior for Input to API: The behavior of this function is undefined unless its control parameter is set to a specific value.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H References
- access.redhat.com/errata/RHSA-2026:13274 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:20611 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:20612 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:20613 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:26319 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:26409 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:29197 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:29794 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:30004 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:30849 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:30850 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:32962 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:33125 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:34372 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:34764 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:34788 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:36004 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:36005 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:36006 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:40762 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:41921 vendor-advisory x_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:58981 vendor-advisory x_refsource_REDHAT
- access.redhat.com/security/cve/CVE-2026-42009 vdb-entry x_refsource_REDHAT
- bugzilla.redhat.com/show_bug.cgi issue-tracking x_refsource_REDHAT
- gnutls.org/security-new.html
Timeline
Related Vulnerabilities
CVE-2024-9053 9.8 vllm: RCE via unsafe pickle deserialization in RPC server
Same package: vllm CVE-2026-25960 9.8 vllm: SSRF allows internal network access
Same package: vllm CVE-2025-47277 9.8 vLLM: RCE via exposed TCPStore in distributed inference
Same package: vllm CVE-2024-11041 9.8 vllm: RCE via unsafe pickle deserialization in MessageQueue
Same package: vllm CVE-2025-32444 9.8 vLLM: RCE via pickle deserialization on ZeroMQ
Same package: vllm