Microsoft Windows up to 11 26H1 Hello Security information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Microsoft Windows 10 21H2/11 23H2/11 24H2/11 25H2/11 26H1. The affected element is an unknown function of the component Hello Security. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2026-27906. The attack must be initiated from a local position. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Microsoft Windows 10 21H2/11 23H2/11 24H2/11 25H2/11 26H1. This affects some unknown functionality of the component Hello Security. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.
The weakness was shared 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-27906. The exploitability is told to be easy. An attack has to be approached locally. Additional levels of successful authentication are needed for exploitation. 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). MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 10.0.19044.7184, 10.0.19045.7184, 10.0.22631.6936, 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
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: 3.3VulDB Meta Temp Score: 2.9
VulDB Base Score: 2.3
VulDB Temp Score: 2.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 4.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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Unproven
EPSS Score: 🔒
EPSS Percentile: 🔒
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.19044.7184/10.0.19045.7184/10.0.22631.6936/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-27906 (🔒)
GCVE (CVE): GCVE-0-2026-27906
GCVE (VulDB): GCVE-100-357429
scip Labs: https://www.scip.ch/en/?labs.20161215
Entry
Created: 04/14/2026 19:44Updated: 04/14/2026 19:47
Changes: 04/14/2026 19:44 (36), 04/14/2026 19:47 (34)
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.