The Windmill API supports scoped API tokens with domain, action, and optional resource/path restrictions. However, the GET /api/w/{workspace}/scripts/list_search endpoint enforces only domain and action scopes at the route level, not the resource/path segment. Consequently, a token scoped to read scripts under a specific path prefix (e.g., scripts:read:f/allowed/*) can retrieve script contents from other paths within the workspace. The endpoint executes a query returning all non-archived scripts in the workspace without per-row filtering by token scope, exposing script source code beyond the token's intended scope. This is a variant of a previously addressed scoped-token authorization issue but remains unpatched for this endpoint. The vulnerability requires possession of a scoped API token but no admin privileges.

An attacker or integration with a scoped API token limited to certain script paths can read script contents from unrelated paths in the same workspace. This may disclose internal automation logic, integration details, business logic, inline configuration, or accidentally hardcoded secrets or credentials. The exposure is limited to the workspace accessible by the token and does not require elevated privileges beyond token possession.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The suggested fix is to enforce resource/path scope filtering in the scripts/list_search handler, either by adding explicit authorization checks or filtering returned scripts by the token's resource scope. Until a patch is available, restrict token issuance carefully and monitor for updates from the vendor. No official fix or patch links are currently provided.