wolfProvider version 1.2.2 is now available. As an OpenSSL 3.x provider, wolfProvider routes cryptographic operations through the wolfCrypt FIPS 140-3 module, allowing existing OpenSSL applications to gain a FIPS-validated cryptographic core without modifying any application code. This release introduces native Windows support, PKCS#8 private-key encryption, FIPS build hardening, and a high severity security fix for AES-GCM in TLS 1.2.
Windows and Visual Studio 2022 Support
wolfProvider now compiles natively on Windows using Visual Studio 2022, building libwolfprov.dll against OpenSSL 3.x and wolfSSL configured via user_settings.h. Both non-FIPS and FIPS configurations are fully supported, bringing the same integration Linux users rely on directly to Windows environments.
PKCS#8 Private-Key Encryption
The PKCS#8 encoder now encrypts private keys whenever a cipher is assigned on the PrivateKeyInfo encoder. This ensures encrypted PKCS#8 output works smoothly through the provider as callers expect. This update also tightens PKCS#8 feature guards and expands cipher-rejection test coverage.
FIPS and Interoperability Enhancements
- Restored the default FIPS policy mask in WOLFSSL_USER_SETTINGS builds, added portable FIPS CAST-mutex initialization, and balanced wolfCrypt init and cleanup calls.
- Stopped advertising SHA-512/224 and SHA-512/256 in FIPS and self-test builds.
- Matched OpenSSL’s ML-KEM NULL output handling.
- Expanded hostap smoke tests and EAP test coverage in CI.
Additional fixes, including X25519 public-key length validation and buffer sizing for ECX/ECC get_params, can be found in the included ChangeLog.
Security Fixes
CVE-2026-81019, AES-GCM Explicit Nonce Reuse on TLS 1.2 and DTLS 1.2
Severity, High. Affects wolfProvider 1.0.0 through 1.2.1.
The 8-byte explicit nonce was generated when setting up the fixed IV, but it did not increment for subsequent records. Because successive AES-GCM records within the same encryption context reused the exact same key and nonce pair, confidentiality was weakened by repeated keystreams and integrity was vulnerable to authentication tag forgery. TLS 1.3, and non-TLS uses of AES-GCM are unaffected. This impacts wolfProvider versions 1.0.0 through 1.2.1 across both FIPS and non-FIPS builds.
Download and Upgrading
Anyone running TLS 1.2 or DTLS 1.2 with AES-GCM through wolfProvider should update to 1.2.2 immediately.
You can find the release on GitHub at https://github.com/wolfSSL/wolfProvider alongside the full ChangeLog.
For questions on wolfProvider, FIPS 140-3, or commercial licensing, reach out to facts@wolfssl.com. For direct technical assistance, contact support@wolfssl.com.
If you have questions about any of the above, please contact us at facts@wolfssl.com or call us at +1 425 245 8247.
Download wolfSSL Now