Is CVE-2026-67541 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-67541 being exploited in the wild.

How severe is CVE-2026-67541?

High severity, with a CVSS score of 8.1, published 11 November 2026.

Is there a fix for CVE-2026-67541?

Yes: fixed in 0.0.70. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67541 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-67541?

Check whether you run Heym at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-67541: Heym team-member management privilege escalation

CVE-2026-67541 · Severity: high · CVSS 8.1 · Published 2026-11-11

Heym is a platform for building and running automated systems and workflows on self-hosted infrastructure. Non-creator team members could exploit weak authorization checks to add attacker accounts to a team and then decrypt all shared credentials (API keys, OAuth tokens) without admin permission. This allows credential theft and potential account takeover of integrated services.

Technologies: Heym. Vendors: Heym.

Quick answers

Is CVE-2026-67541 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67541 being exploited in the wild.
How severe is CVE-2026-67541?: High severity, with a CVSS score of 8.1, published 11 November 2026.
Which products and versions are affected?: Heym prior to 0.0.70.
Is there a fix for CVE-2026-67541?: Yes: fixed in 0.0.70. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67541 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67541?: Check whether you run Heym at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 0.0.70

Technical details

Team-member add/remove/update operations were gated only on team membership rather than requiring creator/admin role, and the TeamMember schema lacked a role column. Any non-creator member could seat an arbitrary account into a team, then access all credentials shared into that team since credential team-shares are scoped only by TeamMember.user_id. The fix restricts these operations to the team creator and adds regression tests.

Affected products

Heym Heym prior to 0.0.70

Timeline

2026-11-11: disclosed
2026-07-04: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.