Microsoft Windows up to Server 2025 Mark of the Web protection mechanism
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $5k-$25k | 0.63- |
Summary
A vulnerability was found in Microsoft Windows. It has been rated as problematic. The affected element is an unknown function of the component Mark of the Web. Performing a manipulation results in protection mechanism. This vulnerability is known as CVE-2026-45595. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in Microsoft Windows. This affects an unknown function of the component Mark of the Web. The manipulation with an unknown input leads to a protection mechanism vulnerability. CWE is classifying the issue as CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. This is going to have an impact on integrity, and availability.
The weakness was published 06/09/2026 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2026-45595. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/09/2026).
Upgrading to version 10.0.19045.7417 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 10 21H2
- 10 22H2
- 10 1607
- 10 1809
- 11 23H2
- 11 24H2
- 11 25H2
- 11 26H1
- Server 2012 R2
- Server 2016
- Server 2019
- Server 2022
- Server 2025
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: 5.4VulDB Meta Temp Score: 4.7
VulDB Base Score: 5.4
VulDB Temp Score: 4.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 5.4
Vendor Vector (Microsoft): 🔒
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: Protection mechanismCWE: CWE-693
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Unproven
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: UpgradeStatus: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Upgrade: Windows 10.0.19045.7417
Timeline
06/09/2026 VulDB entry created06/09/2026 Advisory disclosed
06/09/2026 Countermeasure disclosed
06/09/2026 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-45595 (🔒)
GCVE (CVE): GCVE-0-2026-45595
GCVE (VulDB): GCVE-100-369705
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 06/09/2026 20:14Updated: 06/09/2026 20:18
Changes: 06/09/2026 20:14 (9), 06/09/2026 20:15 (29), 06/09/2026 20:18 (32)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.