Is CVE-2026-100865 exploited in the wild?

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

How severe is CVE-2026-100865?

High severity, with a CVSS score of 8.8, published 27 September 2026.

Is there a fix for CVE-2026-100865?

A patch was published on 2026-09-27: version 0.0.53 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-100865 attacked?

It is attacked over the network.

Am I affected by CVE-2026-100865?

Check whether you run Heymrun 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-100865: Heym multiple RCE and authentication bypass vulnerabilities

CVE-2026-100865 · Severity: high · CVSS 8.8 · Published 2026-09-27

Heym is a workflow automation platform. This advisory covers five independent vulnerabilities affecting versions before 0.0.53: unauthenticated webhook triggers, insecure OAuth handling, plaintext token storage, and Python code execution in workflow conditions. Attackers can execute arbitrary code as the backend user, hijack webhook authentication to trigger workflows with owner privileges, intercept OAuth tokens via malicious redirects, or exploit database leaks to obtain long-lived access tokens.

Technologies: Heymrun Heym. Vendors: Heymrun.

Quick answers

Is CVE-2026-100865 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-100865 being exploited in the wild.
How severe is CVE-2026-100865?: High severity, with a CVSS score of 8.8, published 27 September 2026.
Which products and versions are affected?: Heymrun Heym before 0.0.53.
Is there a fix for CVE-2026-100865?: A patch was published on 2026-09-27: version 0.0.53 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-100865 attacked?: It is attacked over the network.
Am I affected by CVE-2026-100865?: Check whether you run Heymrun 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.

Technical details

The workflow condition evaluator uses unsafe Python eval() without effective sandboxing (CWE-94), reachable by any user editing workflow conditions. Slack and Telegram webhook signature verification fails open when credentials or secrets are absent (CWE-287), allowing unauthenticated trigger activation. OAuth redirect_uri scheme validation is missing (CWE-601), permitting javascript: and data: URIs that intercept authorization codes and execute XSS in the Heym origin. Bearer tokens (WorkflowExecutionToken, PortalSession, HITLRequest.public_token, OAuthAuthorizationCode) are stored in plaintext (CWE-312), exposing valid scoped tokens with 168-hour TTL via database compromise.

Affected products

heymrun Heym before 0.0.53

Timeline

2026-09-27: disclosed
2026-09-27: patched: version 0.0.53

References

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