Why are we reporting so many CVEs? If you follow wolfSSL, you’ve probably noticed the number of CVEs we file per release has ramped up this spring 2026. From 5.8.0 (April 2025) to 5.9.1 (April 2026) we’ve experienced nearly geometric growth in reported CVEs per wolfSSL release. So what’s going on? Should users of wolfSSL […]
Read MoreMore TagCategory: wolfSSL/ wolfCrypt
wolfSSL vs OpenSSL: Heap Usage Comparison
When choosing a TLS library, two questions come up again and again: how much memory does it use and how fast is it. This post focuses on memory, comparing the heap usage of wolfSSL against several OpenSSL releases for an identical TLS 1.2 handshake. All numbers below were regenerated with current releases; wolfSSL 5.9.1 versus […]
Read MoreMore TagNative HTTP Message Signatures in curl, Powered by wolfSSL – Part 3
In Part 1, we argued agents need cryptographic request authenticity. In Part 2 we surveyed the ecosystem and the adjacent tools. This post is about what we’re contributing: native RFC 9421 support at the plumbing layer — curl and libcurl, with wolfCrypt providing the Ed25519 math. Two open PRs: curl — curl/curl#21239 — httpsig: add […]
Read MoreMore TagAnnouncing wolfssl-wolfcrypt Rust Crate v2.0.0
We are pleased to announce the release of wolfssl-wolfcrypt version 2.0.0, now available on crates.io. This major update introduces critical safety enhancements, expanded algorithm support, and architectural changes to improve reliability across different build configurations. Breaking Changes This release includes some breaking API changes necessitated by memory safety and soundness improvements: RNG Ownership: ECC::set_rng, RSA::set_rng, […]
Read MoreMore TagwolfCrypt Performance on the Altera Agilex 5
The Agilex Family and Agilex 5 The Altera Agilex portfolio represents a family of modern SoC FPGAs designed to address the scaling and power efficiency requirements of edge, data center, and communication infrastructures. Built on advanced process technologies, the family unifies programmable logic with hardened processor subsystems, high-bandwidth memory interfaces, and specialized digital signal processing […]
Read MoreMore TagNXP S32K3 Hardware Security Engine (HSE) support using wolfSSL
wolfSSL now supports hardware-accelerated cryptography on the NXP S32K3 family using the on-chip Hardware Security Engine (HSE). The HSE is a secure coprocessor integrated into NXP’s automotive S32K3 microcontrollers. The Hardware Security Engine (HSE) The HSE runs its own firmware on a dedicated core and communicates with the application core over a Messaging Unit (MU). […]
Read MoreMore TagAre You Still Stuck on OpenSSL 1.x.y? We Can Help.
Many organizations still rely on legacy versions of OpenSSL because upgrading certified or long lifecycle products is not always simple. wolfSSL provides lightweight SSL/TLS and cryptography libraries designed for modern embedded and security-focused systems. For compliance-driven environments, wolfCrypt FIPS offers FIPS 140-3 validated cryptography with TLS 1.3 support. If your team is still using OpenSSL […]
Read MoreMore TagwolfSSL Now Runs on CHERI
wolfSSL now builds and runs on CHERI purecap RISC-V, with all of the supporting fixes merged upstream. This brings one of the most widely deployed TLS/SSL and cryptography libraries to a hardware-enforced memory-safety architecture, a natural pairing for the kind of security-critical embedded code wolfSSL is built for. This work was contributed by William Beasley […]
Read MoreMore TagwolfSSL support for ZFS
OpenZFS OpenZFS is a powerful combined filesystem and volume manager, that implements the well-known ZFS filesystem, which supports compressed and encrypted volumes. ZFS was originally developed by Sun Microsystems for Solaris Unix, and the source code was released in 2005 under the OpenSolaris project. Later, in 2013 the OpenZFS project took over open source management […]
Read MoreMore TagDTLS 1.3 in the Linux Kernel: Is There Demand?
We’re building a kernel-native DTLS 1.3 stack — the full wolfSSL handshake and record layer running entirely in Linux kernel context, with no userspace daemon. Before we commit to productizing it, we want to know who needs it. If you encrypt UDP traffic from inside the kernel today, you bounce every packet out to userspace […]
Read MoreMore Tag