Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-114197 Overview
CVE-2026-114197 is an insecure deserialization vulnerability [CWE-502] in Mandiant FLARE capa releases before 10.0.0. The flaw allows arbitrary code execution when a crafted .viv or .exe.viv workspace file is passed to the capa utility. Because capa is widely used by malware analysts to triage samples, a weaponized workspace file can turn the analyst's workstation into the target. Exploitation requires local access and user interaction, but execution occurs in the context of the user running capa.
Critical Impact
An attacker who convinces an analyst to run capa against a crafted .viv or .exe.viv file achieves arbitrary code execution on the analyst workstation.
Affected Products
- Mandiant FLARE capa releases prior to 10.0.0
- Workflows that process untrusted .viv workspace files
- Workflows that process untrusted .exe.viv workspace files
Discovery Timeline
- 2026-10-21 - CVE-2026-114197 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-114197
Vulnerability Analysis
The capa utility, part of the Mandiant FLARE toolkit, loads vivisect workspace files (.viv) to analyze binary samples. Vivisect workspaces are serialized Python objects. When capa deserializes a workspace supplied by the user, it reconstructs objects from the file without validating that the content is safe. An attacker who controls the workspace file can embed objects whose deserialization triggers arbitrary Python code in the analyst's process.
The vulnerability sits in the data-loading path for .viv and .exe.viv files. Because capa typically runs with the privileges of the invoking analyst, execution inherits those privileges and the full malware-analysis toolchain available on the host.
Root Cause
The root cause is deserialization of untrusted data [CWE-502]. The capa codebase before version 10.0.0 reconstructs vivisect workspace objects from file input without a safe loader, allow-list, or integrity check. Any attacker-controlled serialized payload is instantiated during load.
Attack Vector
The attack vector is local and requires user interaction. An attacker delivers a crafted .viv or .exe.viv workspace file to the target, for example alongside a malware sample intended for triage. When the analyst runs capa against the file, deserialization executes the embedded payload. No authentication is required, but the user must actively invoke the vulnerable utility against the attacker-supplied input.
No verified public exploit code is available. See the Mandiant Vulnerability Disclosure MNDT-2026-0035 for technical details.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-114197
Indicators of Compromise
- Unexpected child processes spawned by capa.exe or the capa Python interpreter, particularly shells, scripting hosts, or network utilities.
- .viv or .exe.viv files received from untrusted sources, email attachments, or shared sample repositories.
- Outbound network connections from the analyst workstation initiated immediately after a capa invocation.
Detection Strategies
- Inventory analyst workstations and sandbox hosts for installed capa versions and flag any release earlier than 10.0.0.
- Monitor process-creation telemetry for capa parent processes launching interpreters or LOLBins such as powershell.exe, cmd.exe, python.exe, or curl.
- Alert on file writes to persistence locations (startup folders, scheduled tasks, cron) that occur within the lifetime of a capa process.
Monitoring Recommendations
- Centralize endpoint process and file telemetry from malware-analysis workstations so analyst activity remains auditable.
- Treat malware-analysis hosts as high-value targets and apply the same identification and response coverage used for production endpoints.
- Review capa command-line arguments in logs to surface use against workspace files sourced from untrusted locations.
How to Mitigate CVE-2026-114197
Immediate Actions Required
- Upgrade capa to version 10.0.0 or later on every workstation, sandbox, and automation pipeline that invokes the tool.
- Audit shared sample repositories and triage queues for .viv and .exe.viv files of unknown origin and quarantine them.
- Restrict capa execution to isolated analysis virtual machines that do not have access to production credentials or networks.
Patch Information
Mandiant has released capa version 10.0.0, which remediates the deserialization issue. Refer to the Mandiant Vulnerability Disclosure MNDT-2026-0035 for the fixed release and upgrade guidance.
Workarounds
- Do not pass .viv or .exe.viv workspace files from untrusted sources to capa; regenerate workspaces locally from the original binary instead.
- Execute capa only inside disposable virtual machines or containers with no outbound network access and no sensitive credentials.
- Enforce application-control policies that prevent capa from launching unexpected child processes such as shells or scripting hosts.
# Upgrade capa to a fixed release
pip install --upgrade 'flare-capa>=10.0.0'
# Verify the installed version
capa --version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

