Linux · 
Ubuntu · Package update · May 4, 2026
Ubuntu · Package update · May 4, 2026libgnutls-openssl27 3.5.18-1ubuntu1.6+esm3: libgnutls-openssl27 3.5.18-1ubuntu1.6+esm3 for Ubuntu 18.04.6 LTS (bionic)
libgnutls-openssl27 3.5.18-1ubuntu1.6+esm3, released May 4, 2026, fixes 8 CVEs in libgnutls-openssl27. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.
HighUnsupported product
CVEs closed
8
None rated Critical
Exploited
0
None reported
Highest CVSS
8.2
Base score, 0 to 10
Highest EPSS
0.0161
76th percentile
Priority of the 8 CVEs
Patch now 0
Urgent 0
High 5
Routine 3
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| libgnutls-openssl27 | Ubuntu 18.04.6 LTS (bionic) | 3.5.18-1ubuntu1.6+esm3 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2024-0553 | gnutls-bin: A vulnerability was found in GnuTLS | 7.5 | 0.0161 | None reported |
| High | CVE-2026-42009 | Gnutls: gnutls: denial of service via dtls packet reordering vulnerability | 8.2 | 0.0134 | None reported |
| High | CVE-2026-33846 | gnutls: Fix (DTLS fragment reassembly, High, heap overwrite) | 8.2 | 0.0126 | None reported |
| High | CVE-2026-5260 | gnutls: Fix (PKCS#11 RSA, Medium, heap overread) | 8.2 | 0.0077 | None reported |
| High | CVE-2026-3833 | gnutls: Fix (Name constraints, Medium, name constraint bypass) | 8.2 | 0.0057 | None reported |
| Routine | CVE-2024-12243 | gnutls: quadratic complexity of DER input decoding in libtasn1 can lead to a DoS (bsc#1236974). | 5.3 | 0.0129 | None reported |
| Routine | CVE-2025-14831 | gnutls: Fixed DoS via excessive resource consumption during certificate verification | 5.3 | 0.0066 | None reported |
| Routine | CVE-2025-9820 | gnutls: Fixed buffer overflow in gnutls_pkcs11_token_init | 5.3 | 0.0022 | None reported |
Showing 1 to 8 of 8
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.