CVE-2026-57085 — Windows Print Spooler Information Disclosure Vulnerability
Out-of-bounds read in Windows Print Spooler Components allows an authorized attacker to disclose information locally.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — msrc.microsoft.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2…).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Microsoft | Windows 10 1607 | < 10.0.14393.9339 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows 10 1809 | < 10.0.17763.9020 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows 10 21h2 | < 10.0.19044.7548 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows 10 22h2 | < 10.0.19045.7548 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows 10 Version 1607 | ≥ 10.0.14393.0 and < 10.0.14393.9339 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows 10 Version 1809 | ≥ 10.0.17763.0 and < 10.0.17763.9020 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows 10 Version 21H2 | ≥ 10.0.19044.0 and < 10.0.19044.7548 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows 10 Version 22H2 | ≥ 10.0.19045.0 and < 10.0.19045.7548 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows 11 24h2 | < 10.0.26100.8875 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows 11 25h2 | < 10.0.26200.8875 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows 11 26h1 | < 10.0.28000.2269 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows 11 Version 24H2 | ≥ 10.0.26100.0 and < 10.0.26100.8875 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows 11 Version 25H2 | ≥ 10.0.26200.0 and < 10.0.26200.8875 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows 11 version 26H1 | ≥ 10.0.28000.0 and < 10.0.28000.2525 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2012 | ≥ 6.2.9200.0 and < 6.2.9200.26226 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2012 | version r2versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows Server 2012 (Server Core installation) | ≥ 6.2.9200.0 and < 6.2.9200.26226 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2012 R2 | ≥ 6.3.9600.0 and < 6.3.9600.23291 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2012 R2 (Server Core installation) | ≥ 6.3.9600.0 and < 6.3.9600.23291 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2016 | < 10.0.14393.9339 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows Server 2016 | ≥ 10.0.14393.0 and < 10.0.14393.9339 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2016 (Server Core installation) | ≥ 10.0.14393.0 and < 10.0.14393.9339 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2019 | < 10.0.17763.9020 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows Server 2019 | ≥ 10.0.17763.0 and < 10.0.17763.9020 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2019 (Server Core installation) | ≥ 10.0.17763.0 and < 10.0.17763.9020 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2022 | ≥ 10.0.20348.0 and < 10.0.20348.5386 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2022 | < 10.0.20348.5386 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows Server 2025 | < 10.0.26100.33158 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Windows Server 2025 | ≥ 10.0.26100.0 and < 10.0.26100.33158 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Windows Server 2025 (Server Core installation) | ≥ 10.0.26100.0 and < 10.0.26100.33158 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | secure@microsoft.com via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | microsoft via CVE Program (cve.org) e CISA ADP |
| 3.3 | CVSS 3.1 | Low | 1.8 | 1.4 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · microsoft/windows 10 version 1607, microsoft/windows 10 version 1809, microsoft/windows 10 version 21h2, microsoft/windo
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 3.3
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 2d
- Medium CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 2d
- Medium CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 2d
- Medium CVE-2026-97841 Role: DNS Server Information Disclosure Vulnerability 2d
- Medium CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 2d
- Medium CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-57085 is "Windows Print Spooler Information Disclosure Vulnerability", rated Low. It affects Windows 10 1607 (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.