mbed TLS up to 3.6.3 AESNI Detection compiler optimization removal or modification of security-critical code
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in mbed TLS up to 3.6.3. The impacted element is an unknown function of the component AESNI Detection. The manipulation results in compiler optimization removal or modification of security-critical code. This vulnerability is known as CVE-2025-52496. Attacking locally is a requirement. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability was found in mbed TLS up to 3.6.3. It has been classified as problematic. Affected is an unknown code block of the component AESNI Detection. The manipulation with an unknown input leads to a compiler optimization removal or modification of security-critical code vulnerability. CWE is classifying the issue as CWE-733. The developer builds a security-critical protection mechanism into the software, but the compiler optimizes the program such that the mechanism is removed or modified. This is going to have an impact on confidentiality. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability is traded as CVE-2025-52496 since 06/17/2025. The exploitability is told to be difficult. Local access is required to approach this attack. The technical details are unknown and an exploit is not available.
The vulnerability scanner Nessus provides a plugin with the ID 276316 (TencentOS Server 4: mbedtls (TSSA-2025:0533)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 3.6.4 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (276316) and EUVD (EUVD-2025-20081). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 2.5
VulDB Temp Score: 2.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔒
CNA Base Score: 7.8
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Compiler optimization removal or modification of security-critical codeCWE: CWE-733
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 276316
Nessus Name: TencentOS Server 4: mbedtls (TSSA-2025:0533)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: mbed TLS 3.6.4
Timeline
06/17/2025 CVE reserved07/04/2025 Advisory disclosed
07/04/2025 VulDB entry created
11/24/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2025-52496 (🔒)
GCVE (CVE): GCVE-0-2025-52496
GCVE (VulDB): GCVE-100-314970
EUVD: 🔒
Entry
Created: 07/04/2025 18:49Updated: 11/24/2025 00:25
Changes: 07/04/2025 18:49 (62), 07/04/2025 19:12 (1), 09/23/2025 05:10 (12), 11/24/2025 00:25 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.