Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted malicious archive
-
DeliveryWindows libarchive parses archive
-
ExploitTrigger double free (CWE-415)
-
ExecutionGroom and corrupt heap memory
-
ImpactExecute arbitrary code
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Double free prevention
|
| Exploitation Conditions | Exploitation requires the target system to parse an attacker-supplied, maliciously crafted archive using the Windows-bundled libarchive component (e.g., tar.exe/bsdtar or any application/service that invokes the library). The CVSS vector lists PR:N (no authentication) and UI:N (no interaction), implying an unattended/automated archive-processing context; however, in interactive deployments a user must typically initiate extraction of the hostile archive, which is a meaningful limiting factor. The primary constraint is attack complexity: AC:H reflects that a double free must be won and the resulting heap corruption reliably shaped into code execution, which demands precise heap grooming rather than a deterministic single request. Systems that never process untrusted archives are not realistically exposed. |
| Impact | Signals are mixed, pointing to a serious-but-not-emergency vulnerability. The CVSS 3.1 score of 8.1 (AV:N/AC:H/PR:N/UI:N) reflects a network-reachable, unauthenticated memory-corruption flaw with total CIA impact, but the AC:H flag and CWE-415 (double free) indicate that reliable exploitation requires non-trivial heap manipulation rather than a simple one-shot request. CISA's SSVC framework reinforces a measured posture: Exploitation=none (no observed activity), Automatable=no (cannot be reliably scripted at scale), and Technical Impact=total (full compromise if achieved). No EPSS score, KEV listing, or public POC is present in the provided data, so there is no evidence of active exploitation or available weaponized code. Notable tension to verify: the vector asserts UI:N (no user interaction), yet a double free in an archive-parsing library (libarchive) typically requires the target to open or extract an attacker-supplied archive - the UI:N rating likely assumes an automated service that parses archives unattended; defenders should confirm whether their deployment auto-processes untrusted archives. Overall this is a genuine high-severity patching priority given ubiquitous Windows exposure and total technical impact, but the AC:H rating, SSVC Automatable=no, and absence of exploitation signals argue against treating it as an in-the-wild emergency. |
| Exploit ScenarioDerived | An attacker crafts a malformed archive (e.g., tar/zip) that triggers the double-free condition when parsed by Windows' bundled libarchive (such as tar.exe/bsdtar or any service invoking the library). When the target processes the archive, the double free corrupts heap memory, which a skilled attacker grooms to achieve arbitrary code execution. No public exploit code is identified at time of analysis, and the CVSS AC:H rating indicates reliable exploitation requires careful heap control. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Memory corruption in the libarchive component bundled with Windows (the library behind tar.exe/bsdtar) lets a remote, unauthenticated attacker execute code on affected hosts by having them process a maliciously crafted archive. The root cause is a double free (CWE-415) during archive parsing that corrupts the heap, and because reliably converting that corruption into code execution requires precise heap grooming, Microsoft and our own assessment both rate attack complexity as High despite a CVSS base score of 8.1. No public exploit code has been identified at time of analysis, CISA's SSVC decision framework records exploitation as none and automatable as no, and vendor patches are already available for every affected Windows 10, Windows 11 and Windows Server branch, so this is a serious-but-not-emergency issue that should be closed on a normal patch cadence. One caveat: Microsoft's vector lists UI:N (no user interaction) while our independent assessment uses UI:R, since in interactive deployments a user or application typically has to initiate extraction of the hostile archive - an unattended/service context is where the impact is highest.
RemediationAI
Primary fix: apply the Microsoft security update for CVE-2026-70062 as documented in the vendor advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70062 - patch status is "Patch available per vendor advisory", and the fixed build for each branch is the upper bound of the affected range, i.e. 10.0.22631.7652 (Windows 11 23H2), 10.0.26100.9711 (Windows 11 24H2), 10.0.26200.9711 (Windows 11 25H2), 10.0.28000.3231 (Windows 11 26H1), 10.0.26300.9711 (Windows 11 26H2), 10.0.19044.7807 (Windows 10 21H2/22H2), 10.0.17763.9376 (Windows 10 1809, Server 2019/Server Core), 10.0.20348.5761 (Server 2022) and 10.0.26100.33650 (Server 2025/Server Core). Prioritise internet-facing or service-account processes that unpack attacker-supplied archives, since those match the PR:N/no-interaction portion of the attack surface; note that no public exploit exists at time of analysis, so emergency out-of-band deployment is not required and normal monthly cumulative-update cadence is acceptable. Until every host is patched, compensating controls are to stop untrusted archives from reaching libarchive at all - strip or quarantine archive attachments at the mail/web gateway (trade-off: blocks legitimate .zip/.tar/.7z business mail), block archive MIME types and extensions at the perimeter proxy, and disable or AppLocker/WDAC-restrict tar.exe and third-party utilities that bundle libarchive on servers that have no business extracting archives (trade-off: breaks built-in archive handling and any automation scripts relying on tar.exe, so validate before enforcing). Where archive extraction is a required business function, run it in a disposable, low-privilege container or sandbox with no credential material and no network egress, and require a manual review step before extraction; this does not eliminate the bug but removes the credential and lateral-movement payoff that makes heap corruption worth exploiting. Detection-wise, monitor for unexpected tar.exe/bsdtar child processes spawned by services (IIS, scheduled tasks, mail gateways) and for archive files written to temporary directories immediately preceding such spawns, which is the behaviour profile this double-free path would exhibit.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 13 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Libarchive is an open-source, multi-format archive and compression library (tar, cpio, pax, zip, 7z, rar, xar, ISO, plus gzip/bzip2/xz/zstd filters) that Microsoft ships in-box with Windows and exposes through the bsdtar-based tar.exe utility; any application, script or service that links or shells out to that parser inherits the exposure. The flaw is classified CWE-415 (Double Free): a parser code path releases the same heap buffer twice, creating a dangling reference that an attacker-crafted archive can shape into overlapping allocations, out-of-bounds writes and ultimately attacker-controlled execution in the context of the parsing process. The NVD vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) describes a network-reachable, unauthenticated target with no scope change and full loss of confidentiality, integrity and availability, which implies an automated archive-processing service; our authoritative re-assessment keeps the same impact and AC:H but sets UI:R to reflect the common real-world requirement that a user or application trigger extraction. AC:H is the key qualifier: the double free must be won deterministically and the resulting heap state groomed into a usable corruption primitive, which is far harder than a straightforward single-request bug and is consistent with CISA's SSVC judgement that the issue is not automatable. CPE/version data shows the exposure spans nearly the entire supported Windows client and server line, including Server Core installations, meaning the same library code is present in both GUI and headless environments.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-delivered crafted archive (AV:N) with no auth (PR:N); double-free exploitation needs heap grooming (AC:H); a user typically must extract the archive (UI:R), yielding full RCE impact (C/I/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Double free in Windows Libarchive allows an unauthorized attacker to execute code over a network.
Executive ViewAI
The libarchive library that Microsoft bundles with Windows to power tar.exe and bsdtar contains a memory-corruption flaw, and an affected host that processes a crafted archive could be made to run attacker-supplied code with the privileges of the user or service handling the file. Because tar.exe/bsdtar ships across Windows 10, Windows 11 and every supported Windows Server branch, the exposure spans virtually the entire estate, though Microsoft rates exploitation complexity as High and no public exploit code has been identified at time of analysis. Vendor patches are already available for all affected branches, so leadership should treat this as a broad but manageable exposure to be closed on the normal monthly patch cadence rather than an emergency response.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
EUVD-2026-99146
GHSA-g6pv-h986-vxr8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB