CVE-2025-47917

Exp

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).

Published: 2025-07-20 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-47917 is rated High Exploit Risk (81.5/100): CVSS High severity, with high exploitation likelihood (EPSS 8.43%, 92th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-47917

EDB-ID Source Kind Published Link
52427 exploit_db edb 2025-09-16 Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-47917

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-19 9.90% 8.43% -1.47%
2 2026-05-16 5.16% 9.90% +4.74%
3 2026-05-07 — 5.16% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-47917

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.9 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 6.0 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2025-47917

OS Trackers for CVE-2025-47917

vendor priority summary link
alpine high CVE-2025-47917: 1 source package rows (mbedtls); 90 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 4, open 86. https://security.alpinelinux.org/vuln/CVE-2025-47917
debian not yet assigned CVE-2025-47917 not yet assigned priority: Debian including 1 source packages (mbedtls), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-47917
ubuntu medium CVE-2025-47917 medium priority: Ubuntu including 1 source packages (mbedtls), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): released 5, needed 2, ignored 1. https://ubuntu.com/security/CVE-2025-47917

Affected software / configurations for CVE-2025-47917

Vendor Product Version Raw CPE
arm mbed_tls < 3.6.4 cpe:2.3:a:arm:mbed_tls:*:*:*:*:*:*:*:*

References for CVE-2025-47917

cvelogic Threat Intelligence