Loading vulnerability…
CVE-2026-67429 is an arbitrary file write vulnerability in Flyto2 Core affecting versions prior to 2.26.6. The flaw is rooted in insecure path validation in file-writing functionality, particularly image.download and related modules. Vulnerable code used a caller-controlled output directory as the basis for containment checks instead of enforcing writes through the trusted validate_path_with_env_config mechanism tied to FLYTO_SANDBOX_DIR. In the affected implementation, both the validation base path and the final output path could be influenced by attacker input, allowing path traversal protections to be bypassed and attacker-controlled response bytes to be written to arbitrary filesystem locations accessible to the Flyto2 process. The issue extends beyond a single module, with multiple related file-manipulation modules reportedly lacking equivalent path confinement, broadening the arbitrary write attack surface. The vulnerability was fixed by replacing the flawed validation logic with sandbox-aware path validation that rejects writes outside the configured sandbox.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A path traversal / arbitrary file write vulnerability caused by insecure path validation and missing validation in multiple file-manipulation modules, allowing attacker-controlled output paths to escape intended directory boundaries and create or overwrite files such as cron jobs or SSH authorized_keys.
An arbitrary file write/path traversal vulnerability in Flyto2 Core (flyto-core) prior to version 2.26.6, caused by use of caller-controlled output_dir without proper sandbox path validation, allowing attacker-controlled bytes to be written to arbitrary filesystem paths accessible by the process.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.