GHSA-gxhx-2686-5h9g: slack-go `SecretsVerifier` accepts empty signing secret without precondition
SecretsVerifier in slack-go/slack before v0.23.1 accepts an empty signing secret without error. If an application is misconfigured (e.g., an unset or empty SLACKSIGNINGSECRET), NewSecretsVerifier builds an HMAC-SHA256 keyed with an empty string, allowing an unauthenticated attacker to forge a valid X-Slack-Signature and bypass Slack request authentication.
Published May 14, 2026 · Updated Jun 29, 2026
Affected packages
github.com/slack-go/slack
- Ecosystem
- Go
- Affected
- < 0.23.1
- Fixed in
- 0.23.1
- Check
go list -m github.com/slack-go/slack
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
SecretsVerifier in slack-go/slack before v0.23.1 accepts an empty signing secret without error. If an application is misconfigured (e.g., an unset or empty SLACK_SIGNING_SECRET), NewSecretsVerifier builds an HMAC-SHA256 keyed with an empty string, allowing an unauthenticated attacker to forge a valid X-Slack-Signature and bypass Slack request authentication. Fixed in v0.23.1, which rejects empty secrets with ErrInvalidConfiguration. This is patched in version 0.23.1.
Credited to SnailSploit, massif-01.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
