Physical code execution via Spaceport.sys heap overflow
Published Sep 8, 2026 · Updated Sep 9, 2026
Heap-based buffer overflow in Windows Spaceport.sys allows physically proximate attackers to execute code through a physical interface. Microsoft has not published the affected function, the physical interface involved, or the unchecked input operation that overruns the heap allocation. Exploitation requires physical access to an affected Windows system and grants code execution in the Spaceport.sys driver context.
Summary
What happened
Heap-based buffer overflow in Windows Spaceport.sys allows physically proximate attackers to execute code through a physical interface. Microsoft has not published the affected function, the physical interface involved, or the unchecked input operation that overruns the heap allocation. Exploitation requires physical access to an affected Windows system and grants code execution in the Spaceport.sys driver context.
The record
- CVE
- CVE-2026-71348
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-122
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.17763.0 <10.0.17763.9245
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo