Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-67429.

Unlock with Pro - from £29/user/mo
CVE-2026-67429

Flyto2 Core Arbitrary File Write via image.download Path Traversal (CVE-2026-67429)

Detects exploitation of CVE-2026-67429, a critical (CVSS 10.0) arbitrary file write vulnerability in Flyto2 Core (pip package flyto-core) versions prior to 2.26.7. The image.download module and other file-writing modules fail to sanitize user-supplied filenames/paths (CWE-22 path traversal, CWE-73 external control of file name or path), allowing an unauthenticated or low-privileged attacker to write arbitrary files anywhere on the filesystem reachable by the flyto-core process. This can be leveraged to overwrite application code, cron files, SSH authorized_keys, systemd unit files, or web-accessible directories to achieve remote code execution. Detection focuses on identifying path traversal sequences and absolute/unexpected path targets passed to flyto-core's image.download and related file-writing endpoints, as well as downstream evidence such as newly written files in sensitive directories immediately following flyto-core process activity.

Vulnerability Intelligence

Public PoC

What is CVE-2026-67429 Flyto2 Core Arbitrary File Write via image.download Path Traversal (CVE-2026-67429)?

Flyto2 Core Arbitrary File Write via image.download Path Traversal (CVE-2026-67429) (CVE-2026-67429) maps to the Initial Access and Execution and Persistence tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for Flyto2 Core Arbitrary File Write via image.download Path Traversal (CVE-2026-67429), covering the data sources and telemetry it touches: Process creation logs, File creation/modification logs. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Initial Access Execution Persistence
Microsoft Sentinel / Defender
kusto
let SuspiciousPatterns = dynamic(["..%2f", "..%252f", "..\\\\", "../../", "..%5c", "%2e%2e%2f", "%2e%2e/"]);
let FlytoProc = ProcessCreationEvents
| where FileName has_any ("python", "python3", "gunicorn", "uwsgi", "flyto")
| where ProcessCommandLine has "flyto";
DeviceProcessEvents
| where InitiatingProcessFileName has_any ("python", "python3", "gunicorn", "uwsgi")
| where ProcessCommandLine has "image.download" or ProcessCommandLine has "flyto"
| where ProcessCommandLine has_any (SuspiciousPatterns) or ProcessCommandLine matches regex @"(?i)(\.\.\/){2,}|(\.\.\\\\){2,}"
| project TimeGenerated, DeviceName, AccountName, ProcessCommandLine, InitiatingProcessFileName
| union (
DeviceFileEvents
| where InitiatingProcessCommandLine has "flyto" or InitiatingProcessFileName has_any ("python", "python3", "gunicorn", "uwsgi")
| where FolderPath has_any ("/etc/", "/root/.ssh/", "C:\\Windows\\", "authorized_keys", "/var/www/", "/etc/cron.d/", "wwwroot", "inetpub")
| where ActionType in ("FileCreated", "FileModified")
| project TimeGenerated, DeviceName, AccountName=InitiatingProcessAccountName, ProcessCommandLine=InitiatingProcessCommandLine, InitiatingProcessFileName, FolderPath, FileName
)
| sort by TimeGenerated desc

Detects path traversal sequences passed to Flyto2 Core's image.download module or subsequent file writes to sensitive directories by a flyto-core process, indicating exploitation of CVE-2026-67429.

critical severity medium confidence

Data Sources

Process creation logs File creation/modification logs

Required Tables

DeviceProcessEvents DeviceFileEvents

False Positives

  • Legitimate automated testing or QA scanning of the flyto-core image download endpoint using benign relative paths that happen to match generic patterns
  • Backup or sync tooling that writes to monitored sensitive directories independent of flyto-core
  • Developers debugging flyto-core locally with unusual but non-malicious file paths

Sigma rule & cross-platform mapping

The detection logic for Flyto2 Core Arbitrary File Write via image.download Path Traversal (CVE-2026-67429) (CVE-2026-67429) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: process_creation
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Path Traversal via image.download to /etc/

    Expected signal: Process event for the python3 process with command line referencing flyto_core and a path containing multiple '../' sequences; file creation event for /etc/flyto_poc_test.txt.

  2. Test 2Arbitrary File Write to SSH authorized_keys

    Expected signal: File modification event on /root/.ssh/authorized_keys initiated by the flyto-core python process shortly after a traversal-pattern process command line.

  3. Test 3Path Traversal via image.download on Windows

    Expected signal: Process creation event for python.exe with command line containing flyto and backslash traversal sequences; file creation event under C:\Windows\Temp\.

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-67429 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections