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

8.1 highEPSS 0.4%

High (8.1) in heymrun heym. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page

Severity
Ask an AI about this CVE
Affected
Versions
Attack patterns (CAPEC)
History
References
Your exposure

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.

Severity

CVSS 3.1

8.1 high

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS: 0.4% estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWEs: CWE-266 Incorrect Privilege Assignment
CWE-862 Missing Authorization
OWASP Top 10: A01:2025 Broken Access Control, A06:2025 Insecure Design
Published: 2026-11-11 22:17 UTC
Modified: 2026-11-11 22:17 UTC
Assigned by: GitHub_M (CNA)
NVD analysis: Deferred: the NVD does not plan to analyze it
Record from: the NVD, synced 2026-11-11 22:45 UTC

Ask an AI about this CVE

ChatGPT Claude Google AI Mode

Show the prompt

Explain CVE-2026-67541 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67541?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67541?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67541 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-67541](https://cve.bz/cve/badge/CVE-2026-67541.svg)](https://cve.bz/cve/CVE-2026-67541)

HTML:

<a href="https://cve.bz/cve/CVE-2026-67541"><img src="https://cve.bz/cve/badge/CVE-2026-67541.svg" alt="CVE-2026-67541"></a>

Affected

heymrun:heym

Versions

From the CNA's record in the CVE List.

Product	Affected
heymrun heym	< 0.0.70

Attack patterns (CAPEC)

CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

2026-11-11 The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stack JSON