CVE-2025-47917
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 8.9epss 2.0%
from disclosure to weapon2 days
Published on NVDJul 20
1st PoC+2d
exploitation probability
2.0%top 21% of all CVEs
observed exploitation
nono source reports it
2 public exploit(s)
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).
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H
Affected products
Mbed · mbedtlspublic PoCs found — 2
exploitdbwww.exploit-db.com/exploits/52427unverifiedgithubgithub.com/byteReaper77/CVE-2025-47917★ 1⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://github.com/Mbed-TLS/mbedtls-docs/blob/main/security-advisories/mbedtls-security-advisory-2025-06-7.mdhttps://lists.debian.org/debian-lts-announce/2025/08/msg00013.htmlhttps://lists.debian.org/debian-lts-announce/2025/08/msg00025.htmlhttps://mbed-tls.readthedocs.io/en/latest/tech-updates/security-advisories/