{"answers":{"affected":"2 open source packages ship an affected version, including windmill-api.","exploited":"There is no known exploitation of CVE-2026-54136 in the wild and no public exploit code.","fix":"Upgrade windmill-api to 1.715.0 or later.","what":"CVE-2026-54136 is a medium-severity missing authorization vulnerability in windmill-labs windmill, published on 20 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54136 and fix it if it is affected.\n\nWhat it is: CVE-2026-54136 is a medium-severity missing authorization vulnerability in windmill-labs windmill, published on 20 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54136 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- windmill-api (crates.io): affected all versions; fixed in 1.715.0\n- windmill-api (crates.io): affected all versions; fixed in 1.715.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54136/ (Markdown: https://insights.sbomify.com/CVE-2026-54136/index.md)","id":"CVE-2026-54136","markdown":"https://insights.sbomify.com/CVE-2026-54136/index.md","name":"CVE-2026-54136","record":{"aliases":["GHSA-2ppx-66jv-wpw5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Windmill developer platform","requires_auth":"high_privilege","summary":"Attackers with scoped API tokens can read unauthorized script contents and secrets due to missing path validation in the search endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Windmill: Resource-scoped API tokens can read script contents outside their allowed path via scripts/list_search","id":"CVE-2026-54136","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"http4k: `DigestAuthProvider.verify` ignored configured algorithm and did not bind to request URI","id":"CVE-2026-54147"},"packages":[{"ecosystem":"crates.io","fixed":["1.715.0"],"introduced":["0"],"last_affected":[],"package":"windmill-api","purl":null,"source":"GHSA-2ppx-66jv-wpw5"},{"ecosystem":"crates.io","fixed":["1.715.0"],"introduced":["0"],"last_affected":[],"package":"windmill-api","purl":"pkg:cargo/windmill-api","source":"GHSA-2ppx-66jv-wpw5"}],"prev":{"headline":"AirSane has a Remote Denial of Service (OOM) via Unvalidated Content-Length in HTTP Server","id":"CVE-2026-54135"},"products":["windmill"],"published":"2026-08-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["windmill-labs"]},"summary":"Attackers with scoped API tokens can read unauthorized script contents and secrets due to missing path validation in the search endpoint.","url":"https://insights.sbomify.com/CVE-2026-54136/"}