An exploitable free of a stack pointer vulnerability exists in the x509 certificate parsing code of ARM mbed TLS before 1.3.19, 2.x before 2
An exploitable free of a stack pointer vulnerability exists in the x509 certificate parsing code of ARM mbed TLS before 1.3.19, 2.x before 2.1.7, and 2.4.x before 2.4.2. A specially crafted x509 certificate, when parsed by mbed TLS library, can cause an invalid free of a stack pointer leading to a potential remote code execution. In order to exploit this vulnerability, an attacker can act as either a client or a server on a network to deliver malicious x509 certificates to vulnerable applications.
- Published
- Apr 20, 2017
- Updated
- Jun 16, 2026
- EPSS
- 3.4% · 88th percentile
- CWE
- CWE-295
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.4%
CNA vs NVD score
- NVD
- 8.1
- CNA · talos
- 8.1
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| trustedfirmware | mbed tls | cpe:2.3:a:trustedfirmware:mbed_tls |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- trustedfirmware mbed tlsup to 1.3.18 inclusive
- trustedfirmware mbed tls2.0.0
- trustedfirmware mbed tls2.1.0
- trustedfirmware mbed tls2.1.1
- trustedfirmware mbed tls2.1.2
- trustedfirmware mbed tls2.1.3
- trustedfirmware mbed tls2.1.4
- trustedfirmware mbed tls2.1.5
- trustedfirmware mbed tls2.1.6
- trustedfirmware mbed tls2.4.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (talos). Independent of NVD's CPE analysis and usually ahead of it.
ARM mbed TLS
- 2.4.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | mbedtls | before 2.4.2-r0 | 2.4.2-r0 |
| Debian:12 | mbedtls | before 2.4.2-1 | 2.4.2-1 |
| openSUSE:Tumbleweed | mbedtls-2 | before 2.27.0-1.2 | 2.27.0-1.2 |
| openSUSE:Tumbleweed | mbedtls-3 | before 3.6.6-1.1 | 3.6.6-1.1 |
| SUSE:Package Hub 12 | mbedtls | before 1.3.19-5.1 | 1.3.19-5.1 |
Same product
trustedfirmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-34875An issue was discovered in Mbed TLS through 3.6.5 and TF-PSA-Crypto 1.0.0.39Monitor
- CVE-2024-49195Mbed TLS 3.5.x through 3.6.x before 3.6.2 has a buffer underrun in pkwrite when writing an opaque key pair39Monitor
- CVE-2024-45159An issue was discovered in Mbed TLS 3.x before 3.6.1.39Monitor
- CVE-2024-45158An issue was discovered in Mbed TLS 3.6 before 3.6.1.39Monitor
- CVE-2023-45199Mbed TLS 3.2.x through 3.4.x before 3.5 has a Buffer Overflow that can lead to remote Code execution.39Monitor
- CVE-2026-34873An issue was discovered in Mbed TLS 3.5.0 through 4.0.0.36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:mbedtls | 2.4.2-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:mbedtls | 2.4.2-1 · Debian:12 | Package registry (OSV) |
| opensuse:mbedtls-2 | 2.27.0-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:mbedtls-3 | 3.6.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:mbedtls | 1.3.19-5.1 · SUSE:Package Hub 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) { // Left empty for the test environment}Fixed
val client = OkHttpClient.Builder() .certificatePinner( CertificatePinner.Builder() .add("api.sirius.example", "sha256/…") .build() ).build()Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- security.gentoo.org/glsa/201706-18
- tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-01
Vendor advisories and official records. Exploit/PoC links are deliberately left out.