{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26964 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26964 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26964 is a low-severity vulnerability in windmill-labs windmill, published on 19 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26964 and fix it if it is affected.\n\nWhat it is: CVE-2026-26964 is a low-severity vulnerability in windmill-labs windmill, published on 19 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-26964 in the wild and no public exploit code.\n\nAffected product: windmill-labs windmill. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-26964/ (Markdown: https://insights.sbomify.com/CVE-2026-26964/index.md)","id":"CVE-2026-26964","markdown":"https://insights.sbomify.com/CVE-2026-26964/index.md","name":"CVE-2026-26964","record":{"aliases":["GHSA-f27g-j463-q85w"],"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":"Non-admin users can retrieve Slack OAuth client secrets via an API endpoint, exposing sensitive credentials to unauthorized personnel.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"windmill","vendor":"windmill"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Windmill is an open-source developer platform for internal code: APIs, background jobs, workflows and UIs. Versions 1.634.6\n and below allow non-admin users to obtain Slack OAuth client secrets, which should only be accessible to workspace administrators. The GET /api/w/{workspace}/workspaces/get_settings endpoint returns the slack_oauth_client_secret to any authenticated workspace member, regardless of their admin status. It is expected behavior for non-admin users see a redacted version of workspace settings, as some of them are necessary for the frontend to behave correctly even for non-admins. However, the Slack configuration should not be visible to non-admins. This is a legacy issue where the setting was stored as a plain value instead of using $variable indirection, and it was never added to the redaction logic. This issue has been fixed in version 1.635.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Windmill Exposes Workspace Slack OAuth Client Secrets to Non-Admin Workspace Members","id":"CVE-2026-26964","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FreeRDP has Out-of-bounds Write","id":"CVE-2026-26965"},"packages":[],"prev":{"headline":"Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled","id":"CVE-2026-26963"},"products":["windmill"],"published":"2026-02-19","related":[{"cvss_score":7.3,"headline":"Code injection in windmill","id":"CVE-2026-33881","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":6.9,"headline":"Windmill: SUPERADMIN_SECRET (rarely used) can be accessed publicly","id":"CVE-2026-29059","kev_date_added":null,"published":"2026-03-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-02-20","vendors":["windmill-labs"]},"summary":"Non-admin users can retrieve Slack OAuth client secrets via an API endpoint, exposing sensitive credentials to unauthorized personnel.","url":"https://insights.sbomify.com/CVE-2026-26964/"}