Microsoft Windows up to Server 2025 Push Notification information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.63- |
Summary
A vulnerability was found in Microsoft Windows. It has been classified as problematic. This affects an unknown function of the component Push Notification. This manipulation causes information disclosure. The identification of this vulnerability is CVE-2026-42970. The attack can only be executed locally. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Microsoft Windows. It has been declared as problematic. Affected by this vulnerability is an unknown code block of the component Push Notification. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The weakness was shared 06/09/2026 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. This vulnerability is known as CVE-2026-42970. The exploitation appears to be easy. 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 $0-$5k at the moment (estimation calculated on 06/09/2026). The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Upgrading to version 10.0.17763.8880 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for 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
- 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: 4.4VulDB Meta Temp Score: 3.8
VulDB Base Score: 3.3
VulDB Temp Score: 2.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 5.5
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
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.17763.8880
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-42970 (🔒)
GCVE (CVE): GCVE-0-2026-42970
GCVE (VulDB): GCVE-100-369619
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 06/09/2026 19:25Updated: 06/09/2026 19:29
Changes: 06/09/2026 19:25 (30), 06/09/2026 19:26 (7), 06/09/2026 19:29 (33)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.