CVE-2026-54136
Received Received - Intake

Path Traversal in Windmill Developer Platform

Publication date: 2026-08-20

Last updated on: 2026-08-20

Assigner: GitHub, Inc.

Description
Windmill is an open-source developer platform for internal code: APIs, background jobs, workflows and UIs. Prior to 1.715.0, a resource-scoped API token could read script contents outside its allowed path scope through GET /api/w/{workspace}/scripts/list_search. The route-level scope middleware validated the token domain and action but did not enforce the resource/path segment, and the list_search_scripts handler had no additional check_scopes call or per-row filtering before returning script path and content fields. A token such as scripts:read:f/allowed/* could therefore receive source code for unrelated paths in the same workspace, potentially disclosing internal automation logic, integration details, business logic, inline configuration, or hardcoded secrets and credentials. Exploitation required possession of a valid scoped API token for the workspace but did not require administrator privileges. This issue is fixed in version 1.715.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-20
Last Modified
2026-08-20
Generated
2026-08-20
AI Q&A
2026-08-20
EPSS Evaluated
N/A
NVD
CVE-2026-54136
EUVD
EUVD-2026-63484

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
windmill windmill 1.715.0
windmill_labs windmill to 1.715.0 (exc)
windmill_labs windmill 1.715.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Windmill allows narrowly-scoped API tokens to access script contents outside their permitted path scope. A token with a scope like scripts:read:f/allowed/* could retrieve full script content for all scripts in a workspace via the GET /api/w/{workspace}/scripts/list_search endpoint, not just those within the allowed path. The issue occurred because route-level scope checks only validated domain and action but did not enforce resource or path segments. The fix adds per-row filtering to ensure tokens only access in-scope items.

Detection Guidance

Check Windmill API logs for unusual access to /api/w/{workspace}/scripts/list_search or /api/w/{workspace}/flows/list_search endpoints. Look for tokens with narrow scopes (e.g., scripts:read:f/allowed/*) retrieving content outside their path. Verify if responses include script paths or contents not matching the token's scope.

Impact Analysis

This vulnerability could expose internal automation logic, business secrets, hardcoded credentials, or integration details to unauthorized users. Attackers with a valid scoped token could access sensitive script contents outside their intended scope, potentially leading to data breaches or unauthorized system access. The impact depends on the scripts' sensitivity but could include credential theft or disclosure of proprietary workflows.

Compliance Impact

This vulnerability could violate compliance requirements for data protection and access control, such as GDPR's principle of least privilege or HIPAA's access control safeguards. Unauthorized access to sensitive scripts may result in data exposure, violating confidentiality obligations. Organizations using Windmill must ensure proper token scoping and apply the provided fix to maintain compliance.

Mitigation Strategies

Upgrade Windmill to version 1.715.0 or later to apply the fix. Review and rotate all API tokens, especially those with narrow path scopes. Monitor logs for unauthorized access attempts post-upgrade.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54136. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart