Microsoft Windows up to Server 2025 GDI out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.56 |
Summary
A vulnerability was found in Microsoft Windows. It has been classified as problematic. This affects an unknown function of the component GDI. Performing a manipulation results in out-of-bounds. This vulnerability was named CVE-2026-27930. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in Microsoft Windows. This affects an unknown code block of the component GDI. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality.
The weakness was presented 04/14/2026 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2026-27930. The exploitability is told to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/14/2026).
Upgrading to version 6.2.9200.26026, 6.3.9600.23132, 10.0.14393.9060, 10.0.17763.8644, 10.0.19044.7184, 10.0.19045.7184, 10.0.20348.5020, 10.0.22631.6936, 10.0.25398.2274, 10.0.26100.32690, 10.0.26200.8246 or 10.0.28000.1836 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 10 21H2
- 10 1607
- 10 1809
- 11 23H2
- 11 24H2
- 11 25H2
- 11 26H1
- Server 2016
- Server 2019
- Server 2022
- Server 2022 23H2
- 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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
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 6.2.9200.26026/6.3.9600.23132/10.0.14393.9060/10.0.17763.8644/10.0.19044.7184/10.0.19045.7184/10.0.20348.5020/10.0.22631.6936/10.0.25398.2274/10.0.26100.32690/10.0.26200.8246/10.0.28000.1836
Timeline
04/14/2026 VulDB entry created04/14/2026 Advisory disclosed
04/14/2026 Countermeasure disclosed
04/14/2026 VulDB entry last update
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-27930 (🔒)
GCVE (CVE): GCVE-0-2026-27930
GCVE (VulDB): GCVE-100-357453
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 04/14/2026 19:57Updated: 04/14/2026 20:01
Changes: 04/14/2026 19:57 (35), 04/14/2026 20:01 (35)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.