Mbed mbedtls
Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation. The function mbedtls_x509_string_to_names() takes a head argument that is documented as an output argument. The documentation does not suggest that the function will free that pointer; however, the function does call mbedtls_asn1_free_named_data_list() on that argument, which performs a deep free(). As a result, application code that uses this function (relying only on documented behavior) is likely to still hold pointers to the memory blocks that were freed, resulting in a high risk of use-after-free or double-free. In particular, the two sample programs x509/cert_write and x509/cert_req are affected (use-after-free if the san string contains more than one DN).
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.6.4
Fixed in 3.6.4
Mitigation
Upgrade mbedtls to 3.6.4 or later.
Timeline
Days relative to CVE publicationFirst public PoC 2 days after publication; not in CISA KEV. First PoC: byteReaper77/CVE-2025-47917 (created 22 Jul 2025, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| byteReaper77/CVE-2025-47917 | 22 Jul 2025 +2 d | 1 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| Exploit-DB | Mbed TLS 3.6.4 - Use-After-Free | 16 Sep 2025 | 14 Nov 2026 |