# CVE-2026-69623 — Microsoft Windows 10 Version 1607

> As of 2026-10-08, CVE-2026-69623 is a HIGH-severity vulnerability in Microsoft Windows 10 Version 1607, CVSS v3.1 8, EPSS 0.7% (54.2th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-69623, most recently “Microsoft September 2026 Patch Tuesday — 999 CVEs, 3 actively exploited zero-days (CVE-2026-85880, CVE-2026-81963, CVE-2026-85046)”.

**Last updated:** 2026-10-08

## What is CVE-2026-69623?

Heap-based buffer overflow in Windows HTTP Print Provider allows an authorized attacker to execute code over a network.

The record classifies CVE-2026-69623 under weakness class [CWE-122](https://intel.threadlinqs.com/cwe/CWE-122). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 12 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 44 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **EPSS (FIRST):** 0.7% probability of exploitation in the next 30 days, higher than 54.2% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 6.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-08, last modified 2026-10-08

## Is CVE-2026-69623 being exploited?

It currently carries a trending score of 41 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Microsoft](https://intel.threadlinqs.com/vendors/microsoft): Windows 10 Version 1607, Windows 10 Version 1809, Windows 10 Version 21H2, Windows 10 Version 22H2, Windows 11 version 23H2, Windows 11 Version 23H2, Windows 11 Version 24H2, Windows 11 Version 25H2, Windows 11 version 26H1, Windows Server 2012, Windows Server 2012 (Server Core installation), Windows Server 2012 R2

## How to fix CVE-2026-69623

The record marks a vendor fix as available for CVE-2026-69623. Patch reference: [https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69623](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69623). Vendor advisory: [https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69623](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69623). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-69623

1 tracked threat in the Threadlinqs corpus references CVE-2026-69623, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Microsoft September 2026 Patch Tuesday — 999 CVEs, 3 actively exploited zero-days (CVE-2026-85880, CVE-2026-81963, CVE-2026-85046)](https://intel.threadlinqs.com/threat/TL-2026-2407) — CRITICAL · 2026-09-08

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on 2026-10-10. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [msrc.microsoft.com — vendor advisory](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69623)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-69623
Full detection coverage and IOCs for threats exploiting CVE-2026-69623 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp