CVE-2026-5447 | wolfSSL up to 5.9.0 heap-based overflow
VulDBArchived Apr 10, 2026✓ Full text saved
A vulnerability marked as critical has been reported in wolfSSL up to 5.9.0 . This affects an unknown part. Performing a manipulation results in heap-based buffer overflow. This vulnerability is reported as CVE-2026-5447 . The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-356788 · CVE-2026-5447 · GCVE-0-2026-5447
WOLFSSL UP TO 5.9.0 HEAP-BASED OVERFLOW
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.0 $0-$5k 0.81+
Summaryinfo
A vulnerability described as critical has been identified in wolfSSL up to 5.9.0. This vulnerability affects unknown code. Executing a manipulation can lead to heap-based overflow. This vulnerability appears as CVE-2026-5447. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.
Detailsinfo
A vulnerability classified as critical was found in wolfSSL up to 5.9.0. This vulnerability affects an unknown code block. The manipulation with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Heap buffer overflow in CertFromX509 via AuthorityKeyIdentifier size confusion. A heap buffer overflow occurs when converting an X.509 certificate internally due to incorrect size handling of the AuthorityKeyIdentifier extension.
The weakness was presented by Calif.io. The advisory is shared for download at github.com. This vulnerability was named CVE-2026-5447 since 04/02/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 5.9.1 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Productinfo
Name
wolfSSL
Version
5.0
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9.0
License
open-source
Website
Product: https://github.com/wolfSSL/wolfssl/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Heap-based overflow
CWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: wolfSSL 5.9.1
Patch: github.com
Timelineinfo
04/02/2026 CVE reserved
04/10/2026 +8 days Advisory disclosed
04/10/2026 +0 days VulDB entry created
04/10/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Researcher: Calif.io
Status: Confirmed
CVE: CVE-2026-5447 (🔒)
GCVE (CVE): GCVE-0-2026-5447
GCVE (VulDB): GCVE-100-356788
Entryinfo
Created: 04/10/2026 06:58
Changes: 04/10/2026 06:58 (67)
Complete: 🔍
Cache ID: 99:8E2:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸