Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Evidence used
No CISA KEV confirmation is currently recorded.
EPSS is 0.44% for the current model date.
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.
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-73544
No EUVD known-exploited evidence
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code with a physical attack.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
6.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available
01
What, why and how
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code with a physical attack.
What
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code with a physical attack.
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through physical access may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
What
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code with a physical attack.
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through physical access may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
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 ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.None recorded
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
physical access → Heap-based Buffer Overflow → execute code or commands in the affected security context
Attack surface
Physical
Privileges required
None: unauthenticated exploitation is possible
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-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVPhysicalAttack vector: The attacker needs physical access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
UnauthenticatedRemote code executionCWE-122
A
Official authority intelligence
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2026-73544Official EUVD mapping
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code with a physical attack.
Official EUVD record ↗BSI · German · WID-SEC-2026-3243Microsoft Windows: Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in verschiedenen Versionen von Microsoft Windows Server, Microsoft Windows 10 und Microsoft Windows 11 ausnutzen, um seine Privilegien zu erhöhen, um einen Denial of Service herbeizuführen, um Informationen offenzulegen und um beliebigen Code auszuführen.
Official advisory ↗CERT-FR · French · CERTFR-2026-AVI-1147Multiples vulnérabilités dans Microsoft Windows
embre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69551 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69552 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69553 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69554 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69560 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69561 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69563 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69564 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69566 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69567 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69568 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69569 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69571 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69572 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69573 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69574 du 08 septembre 2026
Bulletin de sécurité Microsoft Windows CVE-2026-69575 du 08 septembre 2026
Bulletin de sécurité Microso
Official advisory ↗CSIRT Italia · Italian · aggiornamenti-mensili-microsoft-24Aggiornamenti Mensili Microsoft
nuova finestra
-
-
CVE-2026-69456 : apre una nuova finestra
-
-
CVE-2026-69457 : apre una nuova finestra
-
-
CVE-2026-69455 : apre una nuova finestra
-
-
CVE-2026-69339 : apre una nuova finestra
-
-
CVE-2026-69458 : apre una nuova finestra
-
-
CVE-2026-69459 : apre una nuova finestra
-
-
CVE-2026-69573 : apre una nuova finestra
-
-
CVE-2026-69453 : apre una nuova finestra
-
-
CVE-2026-69574 : apre una nuova finestra
-
-
CVE-2026-69450 : apre una nuova finestra
-
-
CVE-2026-69571 : apre una nuova finestra
-
-
CVE-2026-69451 : apre una nuova finestra
-
-
CVE-2026-69572 : apre una nuova finestra
-
-
CVE-2026-69445 : apre una nuova finestra
-
-
CVE-2026-69566 : apre una nuova finestra
-
-
CVE-2026-69567 : apre una nuova finestra
-
-
CVE-2026-69443 : apre una nuova finestra
-
-
CVE-2026-69564 : apre una nuova finestra
-
-
CVE-2026-69444 : apre una nuova finestra
-
-
CVE-2026-69449 : apre una nuova finestra
-
-
CVE-2026-69447 : apre una nuova finestra
-
-
CVE-2026-69568 : apre una nuova finestra
-
-
CVE-2026-69448 : apre una nuova finestra
-
-
CVE-2026-69569 : apre una nuova finestra
-
-
CVE-2026-69360 : apre una nuova finestra
-
-
CVE-2026-69481 : apre una nuova finestra
-
-
CVE-2026-69361 : apre una nuova finestra
-
-
CVE-2026-69482 : apre una nuova finestra
-
-
CVE-2026-69480 : apre una nuova fi
Official advisory ↗JVN iPedia · Japanese · JVNDB-2026-033563マイクロソフトのMicrosoft Windows 10 1607等の複数製品におけるヒープベースのバッファオーバーフローの脆弱性
Windows NTFSにおけるヒープベースのバッファオーバーフローにより、不正な攻撃者が物理攻撃を用いてコードを実行できる可能性があります。
Official advisory ↗KISA KrCERT/CC · Korean · KNVD-6946MS 9월 보안 위협에 따른 정기 보안 업데이트 권고
indows Search 구성 요소 변조 취약성 |
| Microsoft Office Word | CVE-2026-69556 | Microsoft Office Word 원격 코드 실행 취약성 |
| Microsoft Teams for Android | CVE-2026-69559 | Android용 Microsoft Teams 정보 유출 취약성 |
| Windows Work Folder Service | CVE-2026-69560 | Windows 작업 폴더 서비스 권한 상승 취약성 |
| Windows CD-ROM Driver | CVE-2026-69561 | Windows CD-ROM 드라이버 권한 상승 취약성 |
| SQL Server | CVE-2026-69562 | Microsoft SQL Server 정보 유출 취약성 |
| Windows Program Compatibility Assistant Service | CVE-2026-69563 | Windows 프로그램 호환성 관리자 서비스 권한 상승 취약성 |
| Windows Online Certificate Status Protocol (OCSP) | CVE-2026-69564 | Windows 온라인 인증서 상태 프로토콜(OCSP) 권한 상승 취약성 |
| Windows NTFS | CVE-2026-69566 | Windows NTFS 원격 코드 실행 취약성 |
| Windows NTFS | CVE-2026-69567 | Windows NTFS 권한 상승 취약성 |
| Windows Storage Spaces Controller | CVE-2026-69568 | 저장소 공간 컨트롤러 정보 유출 취약성 |
| Windows Print Spooler Components | CVE-2026-69569 | Windows 인쇄 스풀러 구성 요소 서비스 거부 취약성 |
| Windows USB Audio Class driver (usbaudio.sys) | CVE-2026-69571 | Windows USB 오디오 클래스 드라이버(usbaudio.sys) 권한 상승 취약성 |
| Windows SMB Client | CVE-2026-69572 | Windows SMB 클라이언트 정보 유출 취약성 |
| Windows Universal Disk Format File System Driver (UDFS) | CVE-2026-69573 | Windows 범용 디스크 형식 파일 시스템 드라이버(UDFS) 권한 상승 취약성 |
| Windows Device Association Service | CVE-2026-69574 | Windows 장치 연결 서비스 권한 상승
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.
Affected versionsThe structured affected or fixed version information changed.
Before
Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9512; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.9245; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7725; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7725; Windows 11 version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.9445; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.9445; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2954; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23397; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23397; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9512; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9512; Windows Server 2019: 10.0.17763.0 < 10.0.17763.9245; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.9245; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5622; Windows Server 2025: 10.0.26100.0 < 10.0.26100.33438; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33438 · 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.9512; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.9245; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7725; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7725; Windows 11 version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.9445; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.9445; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2954; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23398; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23398; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9512; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9512; Windows Server 2019: 10.0.17763.0 < 10.0.17763.9245; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.9245; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5622; Windows Server 2025: 10.0.26100.0 < 10.0.26100.33438; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33438 · 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.
Before
Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9512; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.9245; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7725; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7725; Windows 11 version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.9445; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.9445; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2954; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23397; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23397; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9512; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9512; Windows Server 2019: 10.0.17763.0 < 10.0.17763.9245; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.9245; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5622; Windows Server 2025: 10.0.26100.0 < 10.0.26100.33438; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33438 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9512; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.9245; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7725; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7725; Windows 11 version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.9445; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.9445; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2954; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23397; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23397; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9512; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9512; Windows Server 2019: 10.0.17763.0 < 10.0.17763.9245; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.9245; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5622; Windows Server 2025: 10.0.26100.0 < 10.0.26100.33438; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33438 · 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.
Before
10.0.14393.0 < 10.0.14393.9512; 10.0.17763.0 < 10.0.17763.9245; 10.0.19044.0 < 10.0.19044.7725; 10.0.19045.0 < 10.0.19045.7725; 10.0.22631.0 < 10.0.22631.7582; 10.0.26100.0 < 10.0.26100.9445; 10.0.26200.0 < 10.0.26200.9445 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9512; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.9245; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7725; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7725; Windows 11 version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.7582; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.9445; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.9445; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2954; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26349; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23397; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23397; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9512; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9512; Windows Server 2019: 10.0.17763.0 < 10.0.17763.9245; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.9245; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5622; Windows Server 2025: 10.0.26100.0 < 10.0.26100.33438; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33438 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
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.