OpenSSL 4.1.0: DTLS 1.3 and Faster Post-Quantum Crypto

OpenSSL, the cryptography library underneath a huge share of the internet's encrypted traffic, has shipped version 4.1.0. Released on October 23, 2026, it is a feature release headlined by support for DTLS 1.3, the datagram flavor of modern TLS, plus meaningful speedups for the post-quantum algorithms that will protect data against future quantum computers. For administrators and developers, it is a solid upgrade with a few clearly documented caveats.

• Release date: OpenSSL 4.1.0 was published on GitHub on October 23, 2026
• Headline feature: DTLS 1.3 as defined in RFC 9147, plus DTLS support in the SSL listener API
• Post-quantum speedups: optimized ML-KEM and ML-DSA on ppc64le and ML-DSA on x86_64, including AVX-512 work
• Plan ahead: the project lists four known DTLS issues, with a fix in progress for one

What's New in OpenSSL 4.1.0?

DTLS is TLS adapted for datagram transports such as UDP, which matter for real-time traffic like VoIP, video, gaming and VPN tunnels. Bringing DTLS up to version 1.3 aligns it with the faster, leaner handshake that TLS 1.3 brought to web traffic years ago. The release notes point developers to a new ossl-guide-dtlsv13 manual page for details.

The rest of the feature list:

• RFC 8701 GREASE: random extension values that help keep the TLS ecosystem flexible by catching implementations that choke on unknown extensions
• IKEv2 KDF: a key derivation function used by IPsec VPNs
• AES-CBC acceleration: AVX-512 and VAES optimizations for decryption on x86_64
• New platform: initial support for the Elbrus2000 architecture

How Does OpenSSL 4.1.0 Speed Up Post-Quantum Cryptography?

ML-KEM (for key exchange) and ML-DSA (for digital signatures) are the NIST-standardized algorithms at the heart of the industry's post-quantum migration. OpenSSL 4.1.0 adds optimized NTT operations for both on ppc64le, optimized ML-DSA operations on x86_64, and AVX-512-optimized SHAKE x4 operations for ML-DSA. Faster post-quantum code lowers the performance cost of turning these protections on, which helps every service considering the switch. It fits a broader wave of quantum-ready upgrades, from OpenSSH 10.4's post-quantum defaults to new certificate infrastructure.

Upgrade Notes Before You Deploy

The project is upfront about changes that could affect existing builds:

• Build flags removed: no-ecdsa and no-ecdh are gone because, as the release notes explain, they did not truly disable the code they named; use no-ec instead
• tsget dependency: the timestamp utility now uses Net::Curl::Easy instead of the abandoned WWW::Curl::Easy
• Targets dropped: Windows-on-Itanium and Windows CE are no longer supported
• New MSVC 2013 targets: added to bridge gaps in that compiler's C99 support

Known DTLS Issues to Plan Around

OpenSSL's transparency here is exactly what good open-source security looks like. The release lists four known issues, all in the new DTLS code, as Help Net Security also summarized. Two can cause applications to misread connection state on DTLS listeners, one can make a DTLS 1.3 server abort a handshake after packet loss, and one causes a lost session ticket not to be resent after a KeyUpdate. A fix for the KeyUpdate issue is in progress for a future release.

The practical guidance: if you only use TLS over TCP, these do not touch you. If you plan to adopt DTLS 1.3 or the listener API, test with packet loss in your lab and watch for the follow-up point release. More defensive security news lives in our AI security section.

Sources: OpenSSL 4.1.0 release on GitHub — October 23, 2026; Help Net Security — October 26, 2026.