| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 1.90- |
Summary
A vulnerability, which was classified as problematic, has been found in Microsoft 11 24H2/11 25H2/11 26H1/Server 2025. This issue affects some unknown processing of the component DWM Core Library. This manipulation causes out-of-bounds. The identification of this vulnerability is CVE-2026-48566. The attack can only be executed locally. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in Microsoft 11 24H2/11 25H2/11 26H1/Server 2025 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component DWM Core Library. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality.
The weakness was shared 06/09/2026 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. This vulnerability is known as CVE-2026-48566. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
Upgrading to version 10.0.26100.32772 or 10.0.26100.32860 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
Vendor
Version
License
Website
- Vendor: https://www.microsoft.com/
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: Out-of-boundsCWE: CWE-125 / CWE-119
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: Version 10.0.26100.32772/10.0.26100.32860
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.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-48566 (🔒)
GCVE (CVE): GCVE-0-2026-48566
GCVE (VulDB): GCVE-100-369769
Entry
Created: 06/09/2026 20:49Updated: 06/09/2026 20:52
Changes: 06/09/2026 20:49 (36), 06/09/2026 20:52 (33)
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.