CVE-2026-105534: Windows Storage Remote Code Execution Vulnerability
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.83% (FIRST EPSS); higher than 58.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Windows Server 2016 10.0.14393.9688; Windows Server 2016 (Server Core installation) 10.0.14393.9688; Windows Server 2019 10.0.17763.9487.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Windows Server 2016 10.0.14393.9688; Windows Server 2016 (Server Core installation) 10.0.14393.9688; Windows Server 2019 10.0.17763.9487 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Heap-based buffer overflow in Windows Storage allows an unauthorized attacker to execute code over a network.
- Published
- Nov 10, 2026
- Updated
- Nov 12, 2026
- EPSS
- 0.8% · 58th percentile
- CWE
- CWE-122
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Using windows server 2016? Add it to your stack and be the first to know about CVEs like this one. (Windows Server, Active Directory)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Windows Server 2016
- 10.0.14393.0 and later · before 10.0.14393.9688affected
Microsoft Windows Server 2016 (Server Core installation)
- 10.0.14393.0 and later · before 10.0.14393.9688affected
Microsoft Windows Server 2019
- 10.0.17763.0 and later · before 10.0.17763.9487affected
Microsoft Windows Server 2019 (Server Core installation)
- 10.0.17763.0 and later · before 10.0.17763.9487affected
Microsoft Windows Server 2022
- 10.0.20348.0 and later · before 10.0.20348.5870affected
Microsoft Windows Server 2025
- 10.0.26100.0 and later · before 10.0.26100.33822affected
Microsoft Windows Server 2025 (Server Core installation)
- 10.0.26100.0 and later · before 10.0.26100.33822affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-38076Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability40Plan
- CVE-2021-34458Windows Kernel Remote Code Execution Vulnerability40Plan
- CVE-2026-88243Windows DHCP Server Remote Code Execution Vulnerability39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-47654Jun 9, 2026 · Remote Desktop Client Remote Code Execution Vulnerability30Monitor
- ← EarlierCVE-2026-105520Nov 10, 2026 · Windows DNS Elevation of Privilege Vulnerability28Monitor
- Later →CVE-2026-105557Nov 10, 2026 · Windows DHCP Server Information Disclosure Vulnerability23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Windows Server 2016 | 10.0.14393.9688 · KB5131291 | Microsoft (MSRC) |
| Windows Server 2016 (Server Core installation) | 10.0.14393.9688 · KB5131291 | Microsoft (MSRC) |
| Windows Server 2019 | 10.0.17763.9487 · KB5131085 | Microsoft (MSRC) |
| Windows Server 2019 (Server Core installation) | 10.0.17763.9487 · KB5131085 | Microsoft (MSRC) |
| Windows Server 2022 | 10.0.20348.5870 · KB5131090 | Microsoft (MSRC) |
| Windows Server 2022 (Server Core installation) | 10.0.20348.5870 · KB5131090 | Microsoft (MSRC) |
| Windows Server 2025 | 10.0.26100.33730 · KB5131077 | Microsoft (MSRC) |
| Windows Server 2025 | 10.0.26100.33822 · KB5131080 | Microsoft (MSRC) |
| Windows Server 2025 (Server Core installation) | 10.0.26100.33730 · KB5131077 | Microsoft (MSRC) |
| Windows Server 2025 (Server Core installation) | 10.0.26100.33822 · KB5131080 | Microsoft (MSRC) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recorded+1 d
- TodayNov 12, 2026+2 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-960020 days apartWindows Domain Name Service Remote Code Execution Vulnerability35Monitor
- CVE-2026-960640 days apartWindows Domain Name Service Remote Code Execution Vulnerability35Monitor
- CVE-2026-1137650 days apartWindows File Server Resource Management Service Elevation of Privilege Vulnerability31Monitor
- CVE-2026-882160 days apartWindows DHCP Server Remote Code Execution Vulnerability30Monitor
- CVE-2026-1055600 days apartWindows DHCP Server Remote Code Execution Vulnerability28Monitor
- CVE-2025-49666490 days apartWindows Server Setup and Boot Event Collection Remote Code Execution Vulnerability28Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1501 · Nov 11, 2026(Microsoft Windows Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-122 · Heap-based Buffer OverflowCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.