CVE-2026-70062: Windows libarchive Remote Code Execution Vulnerability
Double free in Windows Libarchive allows an unauthorized attacker to execute code over a network.
Other sources
Windows libarchive Remote Code Execution Vulnerability
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26300.9711Patch KB5127648 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26100.33650Patch KB5126646 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.28000.3231Patch KB5127646 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.22631.7652Patch KB5126653 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26100.9711Patch KB5127648 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.19044.7807Patch KB5126657 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26200.9711Patch KB5127648 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.20348.5761Patch KB5126655 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.17763.9376Patch KB5126651
Event History
Frequently Asked Questions
Which systems should be prioritized for review?
Review Microsoft Windows 10, Windows 11, Windows Server 2019, Windows Server 2022, and Windows Server 2025 systems that use libarchive. The listed impact includes confidentiality, integrity, and availability.
Does exploitation require credentials or user interaction?
The supplied vector indicates no privileges and no user interaction are required. Exploitation is described as occurring over a network, although the attack complexity is rated high.
Is there evidence that this vulnerability is being exploited in the wild?
The provided data marks exploit code maturity as unproven (E:U). It does not provide evidence of active exploitation.
Can the supplied information confirm whether a default Windows installation is affected?
No. The data identifies affected Windows versions and libarchive, but does not state whether libarchive is present or exposed in a default installation.