Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.35% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-59135High confidence
Microsoft Windows Search Component Information Disclosure Vulnerability
Microsoft · Windows 10 Version 1607
5.5MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Low, lowered one band.downgradedsince 29 Sep 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft Windows 10 Version 1607 and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
Weak authentication in Microsoft Windows Search Component allows an authorized attacker to disclose information locally.
What
Weak authentication in Microsoft Windows Search Component allows an authorized attacker to disclose information locally.
Why
The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Weak authentication in Microsoft Windows Search Component allows an authorized attacker to disclose information locally.
Why
The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Weak Authentication → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-1390 ↗
CWE-1390: Weak Authentication. The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Windows Server 2012: 6.2.9200.0 < 6.2.9200.26280
- Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.9121
- Windows Server 2016: 10.0.14393.0 < 10.0.14393.9418
- Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7663
- Windows Server 2025: 10.0.26100.0 < 10.0.26100.33296
- Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.9168
- Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9418
- Windows Server 2019: 10.0.17763.0 < 10.0.17763.9121
- Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26280
- Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23338
- Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2704
- Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7663
- Windows Server 2022: 10.0.20348.0 < 10.0.20348.5499
- Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.9168
- Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.9121
- Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.7517
- Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33296
- Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9418
- Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23338
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 11 Aug 2026 · Last source change 29 Sept 2026, 20:19 UTC · CWE-1390 · Weak Authentication
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-56313
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.14393.0 < 10.0.14393.9418; 10.0.17763.0 < 10.0.17763.9121; 10.0.19044.0 < 10.0.19044.7663; 10.0.19045.0 < 10.0.19045.7663; 10.0.22631.0 < 10.0.22631.7517; 10.0.26100.0 < 10.0.26100.9168; 10.0.26200.0 < 10.0.26200.9168 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9418; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.9121; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7663; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7663; Windows 11 version 23H2: 10.0.22631.0 < 10.0.22631.7517; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.7517; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.9168; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.9168; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2704; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26280; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26280; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23338; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23338; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9418; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9418; Windows Server 2019: 10.0.17763.0 < 10.0.17763.9121; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.9121; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5499; Windows Server 2025: 10.0.26100.0 < 10.0.26100.33296; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33296 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.14393.0 < 10.0.14393.9418; 10.0.17763.0 < 10.0.17763.9115; 10.0.19044.0 < 10.0.19044.7663; 10.0.19045.0 < 10.0.19045.7663; 10.0.22631.0 < 10.0.22631.7517; 10.0.26100.0 < 10.0.26100.9168; 10.0.26200.0 < 10.0.26200.9168 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- 10.0.14393.0 < 10.0.14393.9418; 10.0.17763.0 < 10.0.17763.9121; 10.0.19044.0 < 10.0.19044.7663; 10.0.19045.0 < 10.0.19045.7663; 10.0.22631.0 < 10.0.22631.7517; 10.0.26100.0 < 10.0.26100.9168; 10.0.26200.0 < 10.0.26200.9168 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.