CVE-2026-67541: Heym: Missing role gate in team-member management lets any member add/remove members, exposing team-shared credentials

Published Nov 11, 2026
·
Updated

Heym builds and runs agentic systems and business-process automations on self-hosted infrastructure. Prior to version 0.0.70, team-member management (add / remove / update) is gated only on team membership, not on the team creator/admin role — and TeamMember has no role column. Any non-creator member can seat an attacker account into the team; because credential team-shares are scoped only by TeamMember.userid, the newly-added attacker can then decrypt every credential shared into that team (provider API keys, OAuth tokens. This issue has been patched in version 0.0.70.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Heym to a version that resolves this vulnerability.

    Fixed in 0.0.70

Event History

Nov 11, 2026
CVE Published
via MITRE·09:39 PM
Data Sourced
via MITRE·09:39 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Self-hosted Heym deployments running versions before 0.0.70 are affected where a team has non-creator members and credentials have been shared with that team.

2

What access does an attacker need?

An attacker needs membership in the target team. Any non-creator member can add an attacker-controlled account to the team, without requiring the team creator or admin role.

3

What can a newly added account access?

The added account can decrypt every credential shared into that team, including provider API keys and OAuth tokens. The affected member can also remove or update team members.

4

How can I determine whether exposure may have occurred?

Review team membership changes for accounts added by non-creator members, particularly before upgrading to 0.0.70. Treat credentials shared with teams containing unauthorized additions as potentially exposed.

5

What should be done if patching cannot happen immediately?

Restrict team membership to trusted users and monitor or prevent non-creator members from making membership changes. Rotate provider API keys and OAuth tokens shared with any team where unauthorized membership changes are suspected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203