Slack OAuth secret disclosure via missing redaction
Published Feb 19, 2026 · Updated Feb 20, 2026
Information disclosure in Windmill 1.634.6 and earlier allows remote authenticated users to obtain a workspace Slack OAuth client secret. The get_settings handler returns slack_oauth_client_secret in plaintext because its non-admin response redaction omits that legacy field. Exploitation requires membership in the affected workspace and configured Slack OAuth; the secret permits Slack application impersonation or phishing flows, but not arbitrary Slack message access.
Summary
What happened
Information disclosure in Windmill 1.634.6 and earlier allows remote authenticated users to obtain a workspace Slack OAuth client secret. The get_settings handler returns slack_oauth_client_secret in plaintext because its non-admin response redaction omits that legacy field. Exploitation requires membership in the affected workspace and configured Slack OAuth; the secret permits Slack application impersonation or phishing flows, but not arbitrary Slack message access.
The record
- CVE
- CVE-2026-26964
- Published
- Feb 19, 2026
- Updated
- Feb 20, 2026
- Vendor
- Windmill Labs
- Product
- Windmill
- Classifications
- CWE-200, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.635.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo