Code execution via undocumented deep-free of head list
Published Jul 20, 2025 · Updated Nov 3, 2025
Use-after-free in Mbed TLS before 3.6.4 allows attackers to execute arbitrary code through applications that pass a non-NULL name list. mbedtls_x509_string_to_names() deep-frees the caller-supplied head list although its output-only contract leaves callers retaining pointers to that memory. Exposure requires a direct call with a non-NULL head; internal calls are unaffected, while double-free or later reuse can corrupt memory.
Summary
What happened
Use-after-free in Mbed TLS before 3.6.4 allows attackers to execute arbitrary code through applications that pass a non-NULL name list. mbedtls_x509_string_to_names() deep-frees the caller-supplied head list although its output-only contract leaves callers retaining pointers to that memory. Exposure requires a direct call with a non-NULL head; internal calls are unaffected, while double-free or later reuse can corrupt memory.
The record
- CVE
- CVE-2025-47917
- Published
- Jul 20, 2025
- Updated
- Nov 3, 2025
- Vendor
- TrustedFirmware.org
- Product
- Mbed TLS
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.6.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo