CVE-2026-34874 | mbed TLS up to 3.6.5/4.0.0 null pointer dereference
VulDBArchived Apr 01, 2026✓ Full text saved
A vulnerability described as problematic has been identified in mbed TLS up to 3.6.5/4.0.0 . Impacted is an unknown function. The manipulation results in null pointer dereference. This vulnerability is cataloged as CVE-2026-34874 . The attack may be launched remotely. There is no exploit available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-354745 · CVE-2026-34874 · EUVD-2026-18003
MBED TLS UP TO 3.6.5/4.0.0 NULL POINTER DEREFERENCE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.3 $0-$5k 1.74
Summaryinfo
A vulnerability classified as problematic has been found in mbed TLS up to 3.6.5/4.0.0. The affected element is an unknown function. This manipulation causes null pointer dereference. This vulnerability is registered as CVE-2026-34874. Remote exploitation of the attack is possible. No exploit is available.
Detailsinfo
A vulnerability classified as problematic was found in mbed TLS up to 3.6.5/4.0.0. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:
An issue was discovered in Mbed TLS through 3.6.5 and 4.x through 4.0.0. There is a NULL pointer dereference in distinguished name parsing that allows an attacker to write to address 0.
The advisory is shared at mbed-tls.readthedocs.io. This vulnerability is known as CVE-2026-34874 since 03/31/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-18003).
Productinfo
Name
mbed TLS
Version
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
4.0
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: Null pointer dereference
CWE: CWE-476 / CWE-404
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: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/31/2026 CVE reserved
04/01/2026 +1 days Advisory disclosed
04/01/2026 +0 days VulDB entry created
04/02/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: mbed-tls.readthedocs.io
Status: Not defined
CVE: CVE-2026-34874 (🔒)
GCVE (CVE): GCVE-0-2026-34874
GCVE (VulDB): GCVE-100-354745
EUVD: 🔒
Entryinfo
Created: 04/01/2026 20:47
Updated: 04/02/2026 01:37
Changes: 04/01/2026 20:47 (51), 04/02/2026 01:37 (1)
Complete: 🔍
Cache ID: 99:681:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸