GnuTLS 3.8.13 fixes 12 vulnerabilities affecting secure network communications

GnuTLS 3.8.13 is now available with fixes for 12 security vulnerabilities in the widely used TLS library. The update addresses issues in DTLS packet handling, RSA-PSK authentication, certificate validation, PKCS#11 handling, OCSP validation, and cryptographic padding checks.

The most serious flaws carry high severity ratings and affect areas that matter for secure network communications. These include DTLS reassembly bugs that could cause memory errors and an RSA-PSK username handling issue that could lead to authentication bypass.

Administrators should prioritize the update on servers, appliances, applications, and Linux distributions that rely on GnuTLS for TLS or DTLS communication. Internet-facing services using DTLS or RSA-PSK need the fastest review.

What changed in GnuTLS 3.8.13

The GnuTLS project released version 3.8.13 on April 29, 2026. The release fixes multiple CVE-tracked issues and several additional bugs that affect certificate handling, private key parsing, PKCS#11 support, OCSP processing, and memory safety.

The largest risk area is DTLS reassembly. DTLS protects datagram-based traffic, so flaws in how fragments are sorted, checked, or rebuilt can affect services that process malformed network packets.

The update also fixes certificate validation edge cases. These issues could weaken trust decisions when applications validate names, Subject Alternative Names, OCSP responses, or certificate constraints.

Key vulnerabilities fixed in the update

CVE	Severity	Affected area	Impact
CVE-2026-33846	High	DTLS reassembly	Missing checks could allow a heap overwrite during fragment handling.
CVE-2026-42009	High	DTLS packet sorting	A comparator bug could cause unstable ordering or undefined behavior.
CVE-2026-33845	High	DTLS datagram parsing	A remotely triggerable underflow could lead to a heap overrun.
CVE-2026-42010	High	RSA-PSK authentication	Username truncation with NUL characters could allow authentication bypass.
CVE-2026-3833	Moderate	Name constraints	Case-sensitive domain comparison could cause incorrect certificate acceptance.
CVE-2026-42011	Medium	Name constraints	Permitted constraints could be ignored in some certificate chains.
CVE-2026-42012	Medium	Certificate validation	Certificates with URI or SRV SANs could fall back to Common Name checks.
CVE-2026-42013	Medium	Certificate validation	Oversized SAN handling could incorrectly fall back to Common Name validation.
CVE-2026-42014	Medium	PKCS#11 PIN handling	A PIN change path could trigger a use-after-free.
CVE-2026-5260	Medium	RSA key exchange	Very short premaster secrets could trigger a heap overread with PKCS#11-backed RSA keys.
CVE-2026-42015	Low	PKCS#12 handling	A bounds check bug could write past an internal bag array.
CVE-2026-3832	Low	OCSP validation	A multi-entry OCSP response could cause revoked certificates to be accepted.
CVE-2026-5419	Low	PKCS#7 padding	A non-constant-time padding check could leak timing information.

Why DTLS issues need quick attention

The DTLS fixes stand out because they involve packet parsing and fragment reassembly. Network-facing code that processes malformed packets can create security risk even before normal application logic runs.

CVE-2026-33846 fixes missing checks around DTLS fragments that claimed inconsistent message lengths. GnuTLS also added a missing boundary check to prevent heap overwrite conditions.

CVE-2026-33845 fixes a remotely triggerable underflow in DTLS reassembly. The issue could lead to a heap overrun, which makes it important for services that accept DTLS traffic from untrusted clients.

RSA-PSK authentication bypass is another major fix

CVE-2026-42010 affects servers configured with RSA-PSK. The issue came from how GnuTLS handled usernames containing embedded NUL characters.

In vulnerable cases, a server could match a crafted username against a shorter version of the same name. That creates an authentication bypass risk for environments that still use RSA-PSK configurations.

Organizations should identify whether any exposed services use RSA-PSK. If they do, they should treat GnuTLS 3.8.13 as a priority update rather than a routine library refresh.

Certificate validation fixes reduce trust bypass risks

Several fixes in GnuTLS 3.8.13 address certificate validation behavior. These issues do not all carry the same severity, but they can affect how applications decide whether a certificate should be trusted.

CVE-2026-3833 fixes case-sensitive domain comparison during name constraint processing. The GnuTLS advisory says this violated RFC 5280 rules and could cause domain names to be accepted when they should have been rejected.

The update also changes Common Name fallback behavior when certificates contain URI, SRV, or oversized Subject Alternative Name entries. That reduces the chance that a certificate gets used beyond its intended purpose.

Who should patch first

• Servers and appliances that expose DTLS services to untrusted networks.
• Applications using GnuTLS for TLS or DTLS communication.
• Systems using RSA-PSK authentication with GnuTLS.
• Linux servers that receive GnuTLS through distribution packages.
• Network products, gateways, VPN services, and embedded systems that bundle GnuTLS.
• Security products that parse certificates, OCSP responses, or PKCS#11-backed keys.

What administrators should do now

The main remediation is straightforward. Upgrade to GnuTLS 3.8.13 or a distribution package that includes the same security fixes.

Security teams should also inventory applications that link against GnuTLS. In many environments, the vulnerable library may appear inside operating system packages, containers, embedded appliances, and third-party products.

After patching, teams should restart services that load the library. Updating the package alone may not protect running processes until those services reload the fixed version.

Practical checklist

• Check package versions on Linux servers and containers.
• Review whether exposed services use DTLS.
• Identify any RSA-PSK deployments and prioritize them.
• Patch to GnuTLS 3.8.13 or the fixed vendor package.
• Restart affected services after the update.
• Rebuild container images that include vulnerable GnuTLS packages.
• Ask appliance and software vendors whether their products bundle GnuTLS.
• Monitor for malformed DTLS traffic and unusual authentication failures.

Why library updates matter for network security

GnuTLS sits below many applications. Users may never interact with it directly, but it helps protect connections, certificates, encryption, and authentication in the background.

That makes updates like GnuTLS 3.8.13 important. A single vulnerable cryptographic library can affect many services across an environment, especially when teams do not track where the library appears.

The safest approach is to treat cryptographic library updates as infrastructure security work. Patch quickly, confirm service restarts, and verify that containers and appliances do not keep older builds in production.

FAQ