cve.bz

CVE-2026-87707 microsoft: Heap-based Buffer Overflow

7.8 highEPSS 0.2%Fix available

High (7.8) in microsoft. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Heap-based buffer overflow in Windows Fax and Scan Service allows an authorized attacker to elevate privileges locally.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-122 Heap-based Buffer Overflow
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-87707 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-87707?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-87707?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-87707 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-87707

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-87707](https://cve.bz/cve/badge/CVE-2026-87707.svg)](https://cve.bz/cve/CVE-2026-87707)

HTML:

<a href="https://cve.bz/cve/CVE-2026-87707"><img src="https://cve.bz/cve/badge/CVE-2026-87707.svg" alt="CVE-2026-87707"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.9512
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.9245
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.7725
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.7725
Microsoft Windows 11 version 23H2from 10.0.22631.0 before 10.0.22631.7582
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.7582
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.9445
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.9445
Microsoft Windows 11 version 26H1from 10.0.28000.0 before 10.0.28000.2954
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.26349
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.26349
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.23398
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.23398
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.9512
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.9512
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.9245
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.9245
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.5622
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.33438
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.33438

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON