8.1
CVE-2025-26670
- EPSS 10.43%
- Veröffentlicht 08.04.2025 17:23:50
- Zuletzt bearbeitet 09.07.2025 14:12:36
- Erkennungen
Lightweight Directory Access Protocol (LDAP) Client Remote Code Execution Vulnerability
Use after free in Windows LDAP - Lightweight Directory Access Protocol allows an unauthorized attacker to execute code over a network.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Microsoft ≫ Windows 10 1507 HwPlatform x64 Version < 10.0.10240.20978
Microsoft ≫ Windows 10 1507 HwPlatform x86 Version < 10.0.10240.20978
Microsoft ≫ Windows 10 1607 HwPlatform x64 Version < 10.0.14393.7969
Microsoft ≫ Windows 10 1607 HwPlatform x86 Version < 10.0.14393.7969
Microsoft ≫ Windows 10 1809 HwPlatform x64 Version < 10.0.17763.7136
Microsoft ≫ Windows 10 1809 HwPlatform x86 Version < 10.0.17763.7136
Microsoft ≫ Windows 10 21h2 Version < 10.0.19044.5737
Microsoft ≫ Windows 10 22h2 Version < 10.0.19045.5737
Microsoft ≫ Windows 11 22h2 Version < 10.0.22621.5189
Microsoft ≫ Windows 11 23h2 Version < 10.0.22631.5189
Microsoft ≫ Windows 11 24h2 Version < 10.0.26100.3775
Microsoft ≫ Windows Server 2008 Version - Update sp2 HwPlatform x64
Microsoft ≫ Windows Server 2008 Version - Update sp2 HwPlatform x86
Microsoft ≫ Windows Server 2008 Version r2 Update sp1 HwPlatform x64
Microsoft ≫ Windows Server 2012 Version -
Microsoft ≫ Windows Server 2012 Version r2
Microsoft ≫ Windows Server 2016 Version < 10.0.14393.7969
Microsoft ≫ Windows Server 2019 Version < 10.0.17763.7136
Microsoft ≫ Windows Server 2022 Version < 10.0.20348.3453
Microsoft ≫ Windows Server 2022 23h2 Version < 10.0.25398.1551
Microsoft ≫ Windows Server 2025 Version < 10.0.26100.3775
VulnDex Vulnerability Enrichment
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 10.43% | 0.952 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| Microsoft | 8.1 | 2.2 | 5.9 |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-26670