dbcve.org
WindmillApplication

CVE-2026-29059

HIGH · 7.5 CVSS v3.1 Published 2026-03-06
Fix available
A fix is available. Upgrade to 1.603.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windmill is an open-source developer platform for internal code: APIs, background jobs, workflows and UIs. Prior to version 1.603.3, an unauthenticated path traversal vulnerability exists in Windmill's get_log_file endpoint "(/api/w/{workspace}/jobs_u/get_log_file/{filename})". The filename parameter is concatenated into a file path without sanitization, allowing an attacker to read arbitrary files on the server using ../ sequences. This issue has been patched in version 1.603.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unauthenticated path traversal vulnerability exists in Windmill's get_log_file endpoint (/api/w/{workspace}/jobs_u/get_log_file/{filename}) where the filename parameter is directly concatenated into a file path without sanitization. Attackers can use '../' sequences to traverse directories and read arbitrary files on the server, leading to potential sensitive data exposure.

MitigationUpgrade Windmill to version 1.603.3 or later, which contains the patch for proper path sanitization in the get_log_file endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WindmillApplication
Affected:< 1.603.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windmill version
    Inspect the Windmill instance version by querying the /api/version endpoint or checking the running container/service metadata
    Affected if The installed version is any version prior to 1.603.3
  2. Verify the get_log_file endpoint exists
    Confirm the Windmill server exposes the /api/w/{workspace}/jobs_u/get_log_file/{filename} endpoint by reviewing the exposed API routes or attempting a request to the endpoint
    Affected if The endpoint is available and responds to requests
  3. Determine if endpoint requires authentication
    Test unauthenticated access to the get_log_file endpoint by sending a request without any authorization headers
    Affected if The endpoint responds to unauthenticated requests (no 401 or 403 error)
  4. Test for path traversal vulnerability
    Send a request to the get_log_file endpoint with a path traversal sequence such as ../../etc/passwd in the filename parameter
    Affected if The server returns content from files outside the intended log directory, confirming the vulnerability exists

A Windmill instance is affected if it runs a version prior to 1.603.3 and exposes the get_log_file endpoint to unauthenticated users without additional access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.603.3 or later
Fixed in 1.603.3
Interim mitigation

Upgrade Windmill to version 1.603.3 or later, which contains the patch for proper path sanitization in the get_log_file endpoint.

Recommended fix High confidence

Windmill version 1.603.3

  1. Identify your current Windmill installation method (e.g., Docker, binary, Helm, etc.)
  2. Stop the currently running Windmill instance
  3. Back up your Windmill data and configuration
  4. Retrieve and install Windmill version 1.603.3 using your installation method
  5. Verify the installation was successful
  6. Restart the Windmill service
  7. Confirm the vulnerability is no longer present by testing the /api/w/{workspace}/jobs_u/get_log_file/{filename} endpoint

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windmill Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-29059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-29059 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data