CVE-2026-100862: heym before 0.0.91 Multiple Secrets Plaintext Storage
heym, a workflow automation platform, stores and returns multiple capability secrets in plaintext in versions prior to 0.0.91. Affected secrets include webhook header-auth values (returned in cleartext by GET /api/workflows/{id} and persisted unsanitized into execution history), MCP API keys (stored as a plaintext column, returned in config/list responses, and accepted via the ?key= query string so they leak into logs, proxies and Referer headers), portal session tokens (stored and validated by plaintext equality with a 168-hour TTL), workflow execution JWTs (stored in full and re-listed by GET .../execution-tokens), Discord interaction tokens (the full interaction body is stored in execution history), and global variables. A user with read access to a workflow, share/team membership, or anyone able to read the database, a backup, or logs can recover these secrets and replay them to execute workflows or act as the secret owner.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
heymto a version that resolves this vulnerability.Fixed in 0.0.91
Event History
Frequently Asked Questions
Who can recover and replay the exposed secrets?
Any user with read access to a workflow or share/team membership may be able to retrieve secrets exposed through workflow and configuration responses. Anyone who can read the database, backups, or logs can also recover plaintext secrets and potentially replay them to execute workflows or act as the secret owner.
Which deployment artifacts should be treated as potential sources of leaked credentials?
Review workflow API responses, execution history, configuration and list responses, execution-token listings, the database, backups, and application or proxy logs. MCP API keys are especially likely to appear in logs, proxies, and Referer headers when supplied through the key query parameter.
Are portal sessions and workflow execution tokens exposed in a reusable form?
Yes. Portal session tokens are stored and validated using plaintext equality and have a 168-hour TTL, while workflow execution JWTs are stored in full and re-listed through execution-token endpoints. Recovered values may be replayed while they remain valid.
What should be done if affected secrets may have been exposed before remediation?
Treat affected webhook authentication values, MCP API keys, portal session tokens, workflow execution JWTs, Discord interaction tokens, and global variables as potentially compromised. Rotate or invalidate secrets where supported and investigate access to workflow data, databases, backups, and logs.