The OpenSSL Project published OpenSSL 4.1.0 on October 23, 2026, delivering a major feature release that substantially upgrades the cryptographic foundation of internet servers, enterprise networking appliances, and operational software. Representing hundreds of commits to the core codebase since version 4.0, the release focuses on two architectural imperatives: establishing native support for Datagram Transport Layer Security 1.3 (DTLS 1.3) and accelerating post-quantum cryptographic primitives through specialized microprocessor vector extensions.
At the protocol layer, version 4.1.0 officially implements RFC 9147, bringing DTLS 1.3 into the core runtime and the unified SSL listener API. Designed to provide transport security over datagram protocols like UDP, DTLS 1.3 aligns datagram encryption with TLS 1.3 by eliminating legacy cryptographic suites, enforcing perfect forward secrecy, and streamlining connection handshakes. To protect future protocol extensibility from hostile network intermediaries, OpenSSL 4.1.0 also implements RFC 8701 GREASE (Generate Random Extensions And Sustain Extensibility), which injects reserved pseudo-random protocol identifiers into handshakes to prevent middlebox vendors from hardcoding brittle packet filters.
To address the approaching transition toward post-quantum cryptography, maintainers engineered dedicated hardware acceleration routines for NIST's standardized lattice algorithms. The release adds optimized Number Theoretic Transform (NTT) operations for ML-KEM and ML-DSA on 64-bit Little-Endian PowerPC (ppc64le) architectures, alongside hand-tuned x86_64 assembly. Furthermore, OpenSSL 4.1.0 leverages AVX-512 vector pipelines to deliver four-way parallel SHAKE operations for ML-DSA signature verification, while utilizing AVX-512 and Vector AES (VAES) instructions to accelerate AES-CBC decryption throughput.
Alongside functional enhancements, the project executed housekeeping across legacy configurations. The release permanently purges build configurations for Windows-on-Itanium (VC-WIN64I) and Windows CE (VC-CE), while removing deprecated dummy options like no-ecdsa and no-ecdh in favor of unified elliptic curve configuration flags. Maintainers highlighted two known runtime caveats in the 4.1.0 tarball: issue #32878, where receiving a DTLS 1.3 KeyUpdate message prematurely flushes outstanding post-handshake records from retransmission buffers, and issue #33277 regarding listener error reporting under permanent receive failures.