OpenSSL has formally launched version 4.1.0, integrating Datagram Transport Layer Security (DTLS) 1.3 support alongside performance boosts and steps toward post-quantum resistance. While not a security patch per se, the release introduces several major features and compatibility changes, plus four known issues users should assess before deployment.
What’s New in OpenSSL 4.1.0
Leading the improvements is the addition of DTLS 1.3 (specified in RFC 9147), which mirrors many of TLS 1.3’s protections—handling eavesdropping, tampering, and message forging—while adapting to the unordered, unreliable nature of datagram protocols like UDP. That means better support for applications where low latency is critical, such as real-time streaming or gaming.
Other notable enhancements include GREASE (Generate Random Extensions And Sustain Extensibility) to guard against ossification of protocol extensions, an IKEv2 key derivation function, and initial support for the Elbrus2000 CPU architecture. For specific platform enhancements, ppc64le machines gain optimized ML-DSA and ML-KEM number theoretic transform operations. On x86_64, there are improvements in ML-DSA, AVX-512 SHAKE operations, and faster AES-CBC decryption using AVX-512 and VAES. There’s no benchmark data yet to quantify those gains.
Deprecations, Compatibility and Known Gaps
Version 4.1.0 also revises build and configuration targets: it removes Windows-on-Itanium and Windows CE build support, adds fixes for MSVC 2013’s C99 compliance gaps, and changes how elliptic curve options work—‘no-ecdsa’ and ‘no-ecdh’ settings have been dropped since they didn’t disable those parts effectively. Users wanting to disable elliptic curve operations must now use ‘no-ec’.
There are four documented problems wrapped up in this release. A DTLS 1.3 KeyUpdate message could accidentally drop other pending post-handshake records from the retransmission buffer, meaning lost elements like session tickets could fail to resend if the original packets are lost. Listener error handling may misreport permanent receive failures as SSL_ERROR_WANT_READ, leading to hangs; write failures may appear as SSL_ERROR_SYSCALL, risking premature connection closure. Also, packet loss followed by early client acknowledgments can trigger handshake failures. A fix is expected in a subsequent update.
Additionally, developers relying on tsget must install the Net::Curl::Easy module, replacing the previously used WWW::Curl::Easy. This version also introduces some compatibility breakage, so testing complex DTLS or elliptic curve setups is highly advised before moving to production.
OpenSSL 4.1.0 was published on October 23, 2026. Its status is a feature release; it does not primarily address security vulnerabilities. The security team is aware of earlier memory-leak issues which have been patched, and separate from these known problems in the 4.1.0 release series.
Why this matters: DTLS plays a critical role wherever low latency over UDP is essential—think VoIP, gaming, streaming, or IoT. Equally, post-quantum improvements signal a shift in cryptographic priorities. But the documented bugs—particularly involving session tickets and error handling—could introduce real risks in production, especially in high-availability and secure environments.
