Microsoft Windows up to Server 2025 CryptoAPI inadequate encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.5 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Microsoft Windows 11 24H2/11 25H2/11 26H1/Server 2022/Server 2025. Impacted is an unknown function of the component CryptoAPI. This manipulation causes inadequate encryption. The identification of this vulnerability is CVE-2026-55144. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability classified as problematic was found in Microsoft Windows 11 24H2/11 25H2/11 26H1/Server 2022/Server 2025. Affected by this vulnerability is some unknown processing of the component CryptoAPI. The manipulation with an unknown input leads to a inadequate encryption vulnerability. The CWE definition for the vulnerability is CWE-326. The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. As an impact it is known to affect confidentiality. The summary by CVE is:
Missing cryptographic step in Windows CryptoAPI allows an authorized attacker to perform tampering locally.
It is possible to read the advisory at msrc.microsoft.com. This vulnerability is known as CVE-2026-55144 since 06/16/2026. The exploitation appears to be difficult. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/14/2026). The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.5VulDB Meta Temp Score: 2.5
VulDB Base Score: 2.5
VulDB Temp Score: 2.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Inadequate encryptionCWE: CWE-326 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/16/2026 CVE reserved07/14/2026 Advisory disclosed
07/14/2026 VulDB entry created
07/14/2026 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-55144 (🔒)
GCVE (CVE): GCVE-0-2026-55144
GCVE (VulDB): GCVE-100-378559
Entry
Created: 07/14/2026 21:55Changes: 07/14/2026 21:55 (53)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.