Windmill Under Attack: Active Path Traversal on 170 Exposed…

CVE-2026-29059 hits the Windmill automation platform with an unauthenticated path traversal. A patch has existed since January, yet thousands of instances remain vulnerable.

An unauthenticated path traversal vulnerability in the Windmill automation platform has been under active exploitation since July 22, 2026. The flaw, tracked as CVE-2026-29059, allows arbitrary file reads on the server via the /api/w/{workspace}/jobs_u/get_log_file/{filename} endpoint, with potential escalation to superadmin when the SUPERADMIN_SECRET environment variable is configured. Roughly 170 exposed systems across 24 countries remain vulnerable despite the fix being available since January.

Key Takeaways

The Windmill get_log_file endpoint concatenates the filename parameter without sanitization, allowing ../ sequences to read arbitrary files
VulnCheck detected active exploits targeting /etc/passwd and /proc/1/environ, with approximately 170 vulnerable instances exposed on the internet across 24 countries
When SUPERADMIN_SECRET is set, reading it from /proc/1/environ enables authentication as superadmin via Bearer token
Windmill version 1.603.3, released in January 2026, patches the vulnerability; active exploitation demonstrates the fix has not been widely applied

The Mechanism: How the Path Traversal Works on get_log_file

The REST endpoint /api/w/{workspace}/jobs_u/get_log_file/{filename} receives the filename as a path parameter and concatenates it directly into the filesystem path without sanitization. According to the March 2026 Windmill advisory, cited by The Hacker News: "The filename parameter is concatenated into a file path without sanitization, allowing an attacker to read arbitrary files on the server using ../ sequences."

The National Vulnerability Database assigns the flaw a CVSS 3.1 score of 7.5 (HIGH), with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. The severity stems from network access without authentication and the complete absence of privilege or user interaction requirements. Impact is limited to confidentiality: arbitrary file reads, with no direct integrity or availability compromise.

The simplicity of the vector — a single HTTP request with directory traversal sequences — makes it particularly suited to automated scanning and maximizing attacker yield.

From File Read to Full Control: The Role of SUPERADMIN_SECRET

The base impact of the vulnerability is arbitrary file reads, but the operational configuration drastically amplifies the stakes. When an administrator has set the SUPERADMIN_SECRET environment variable, it becomes readable via /proc/1/environ, the init process file of the container that exposes all environment variables.

The extracted token is directly usable as a Bearer token for the job preview API, enabling code execution with superadmin privileges. According to the Windmill advisory cited by The Hacker News: "The primary sensitive value exposed by this vulnerability is the SUPERADMIN_SECRET environment variable, readable via /proc/1/environ."

The variable is not set by default in standalone installations, which therefore remain limited to file reads only. However, enterprise deployments and containerized integrations — where SUPERADMIN_SECRET is configured to enable advanced administrative features — turn the path traversal into a full platform compromise vector.

Nextcloud Flow: When Integration Becomes an Aggravating Factor

A distinct risk vector emerges in installations that embed Windmill via Nextcloud Flow. According to SecNews technical analysis, which cites a Nextcloud advisory, in this configuration the windmill_users_config.json file exposes administrative tokens in cleartext. The combination of the Windmill path traversal with the Nextcloud credential leak enables remote code execution as root in the container.

Caitlin Condon, VP of security research at VulnCheck, confirmed via LinkedIn that observed exploits target both direct Windmill endpoints and Nextcloud proxy paths: "We've observed exploits aimed at both direct Windmill endpoints and the Nextcloud proxy path."

The dual attack surface — standalone Windmill installations and Nextcloud Flow deployments — explains the broad geographic distribution and persistence of exploitation even after public disclosure.

The Time Problem: Six Months of an Ignored Patch

Windmill version 1.603.3, which introduces filename parameter sanitization checks, was released in January 2026. The CVE was disclosed in March 2026. Active exploitation is documented from July 22, 2026. The interval of at least six months between patch and mass exploitation illustrates a recurring pattern in internal automation platforms.

Windmill is typically deployed as an orchestration tool for enterprise workflows, often in subnets considered protected or with limited exposure. This perception of an "internal tool" reduces the priority of patch management processes, turning instances into low-visibility targets for attackers. According to VulnCheck data cited by National CIO Review, the roughly 170 vulnerable exposed instances are distributed across 24 countries, with a presumed concentration in cloud and containerized environments.

The misalignment between fix availability and operational application is not technical but organizational: development and automation platforms often lack the automatic update pipelines that characterize customer-facing production services.

"Roughly 170 exposed Windmill systems across 24 countries are vulnerable to CVE-2026-29059, with active exploits documented by VulnCheck against /etc/passwd and /proc/1/environ"

What to Do Now

Priority actions for organizations using Windmill derive directly from the documented facts:

Immediately update to Windmill 1.603.3 or later, verifying that filename parameter sanitization is active in the deployed configuration
Check whether SUPERADMIN_SECRET is configured on exposed instances; if so, rotate the value after patching as it may have been compromised
Review access logs for the get_log_file endpoint for ../ sequences or requests to /proc/1/environ and /etc/passwd, indicators of the observed exploit
Assess internet exposure of Windmill instances, including those reachable via Nextcloud proxy, and reduce attack surface where external access is not required

The Lesson: Developer Tools Are the Last Missing Link

The story of CVE-2026-29059 is not that of a sophisticated zero-day but of a forgotten patch in a category of software — internal automation platforms — that organizations do not classify as critical. The low visibility of Windmill instances, the lack of automatic update processes, and the assumption that "it's not exposed" create a systemic gap that attackers know how to exploit.

The Nextcloud Flow case adds a specific element: when automation platforms are integrated into broader ecosystems, compromise of a secondary component propagates with elevated privileges into the primary system. Credential rotation, in this scenario, is not an optional post-patch measure but a mandatory step because the duration of the exposure window prior to the update remains indeterminate.

The VulnCheck figure of 170 vulnerable systems across 24 countries, while representing a relatively contained surface, indicates a distributed and persistent presence that requires targeted intervention rather than generalized alarmism. The challenge is identifying these instances in your own environments before attackers do.

Sources

Information has been verified against cited sources and updated at time of publication.

Sources

Sources and references