heymrun Heym up to 0.0.69 Team Member Management privileges management

Summaryinfo

A vulnerability classified as critical was found in heymrun Heym up to 0.0.69. This affects an unknown function of the component Team Member Management. Executing a manipulation can lead to privileges management. The identification of this vulnerability is CVE-2026-67541. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as critical was found in heymrun Heym up to 0.0.69. This vulnerability affects an unknown function of the component Team Member Management. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.user_id, 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.

The advisory is available at github.com. This vulnerability was named CVE-2026-67541 since 07/29/2026. The exploitation appears to be easy. The attack can be initiated remotely. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.

Upgrading to version 0.0.70 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• heymrun

Name

• Heym

Version

• 0.0.1
• 0.0.2
• 0.0.3
• 0.0.4
• 0.0.5
• 0.0.6
• 0.0.7
• 0.0.8
• 0.0.9
• 0.0.10
• 0.0.11
• 0.0.12
• 0.0.13
• 0.0.14
• 0.0.15
• 0.0.16
• 0.0.17
• 0.0.18
• 0.0.19
• 0.0.20
• 0.0.21
• 0.0.22
• 0.0.23
• 0.0.24
• 0.0.25
• 0.0.26
• 0.0.27
• 0.0.28
• 0.0.29
• 0.0.30
• 0.0.31
• 0.0.32
• 0.0.33
• 0.0.34
• 0.0.35
• 0.0.36
• 0.0.37
• 0.0.38
• 0.0.39
• 0.0.40
• 0.0.41
• 0.0.42
• 0.0.43
• 0.0.44
• 0.0.45
• 0.0.46
• 0.0.47
• 0.0.48
• 0.0.49
• 0.0.50
• 0.0.51
• 0.0.52
• 0.0.53
• 0.0.54
• 0.0.55
• 0.0.56
• 0.0.57
• 0.0.58
• 0.0.59
• 0.0.60
• 0.0.61
• 0.0.62
• 0.0.63
• 0.0.64
• 0.0.65
• 0.0.66
• 0.0.67
• 0.0.68
• 0.0.69

Website

• Product: https://github.com/heymrun/heym/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion