CVE-2025-52496
Arm Mbed Tls vulnerability
- Published4 Jul 2025
Description
Mbed TLS before 3.6.4 has a race condition in AESNI detection if certain compiler optimizations occur. An attacker may be able to extract an AES key from a multithreaded program, or perform a GCM forgery.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-52496 being actively exploited?
CVE-2025-52496 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.21%.
How severe is CVE-2025-52496?
CVE-2025-52496 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.21% probability of exploitation.
Which products are affected by CVE-2025-52496?
Affected products include Arm Mbed Tls.
How do I fix CVE-2025-52496?
Upgrade affected software to a fixed version, for example Arm Mbed Tls 3.6.4 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-52496 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.