CVE-2026-100865
Last modified
CVE-2026-100865 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. Heym before 0.0.53 contains multiple independent vulnerabilities. (1) The workflow condition evaluator uses Python eval() without an effective sandbox, allowing any user who can edit a workflow branch/condition node — or who can import a workflow template containing a malicious condition node — to execute arbitrary Python code as the backend process user when the workflow runs.
Description
Heym before 0.0.53 contains multiple independent vulnerabilities. (1) The workflow condition evaluator uses Python eval() without an effective sandbox, allowing any user who can edit a workflow branch/condition node — or who can import a workflow template containing a malicious condition node — to execute arbitrary Python code as the backend process user when the workflow runs. (2) Slack webhook signature verification and (3) Telegram webhook secret-token verification fail open when the trigger node has no credentialId or an empty signing secret, allowing anyone who knows the public webhook URL to trigger workflows with the owner's credentials without authentication. (4) The OAuth authorization endpoint does not validate the redirect_uri scheme, so an attacker who registers a public OAuth client with a javascript: or data: redirect_uri and lures a victim to the consent screen receives the authorization code and executes attacker-controlled JavaScript in the Heym origin, including access to the victim's HttpOnly auth cookie. (5) WorkflowExecutionToken, PortalSession, HITLRequest.public_token, and OAuthAuthorizationCode values are stored in plaintext, so any database read exposure yields valid scoped bearer tokens, including portal and HITL tokens with a 168-hour TTL that permit workflow execution on behalf of the owner.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| heymrun | heym | < 0.0.53 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-100865?
How severe is CVE-2026-100865?
How do I fix CVE-2026-100865?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-10086GitLab has remediated an issue in GitLab EE affecting all ve…5.4
- CVE-2026-100860heym before 0.0.105 does not act on the result of the creden…5.5
- CVE-2026-100861heym before 0.0.105 fails to apply egress guards to integrat…5
- CVE-2026-100862heym, a workflow automation platform, stores and returns mul…4.9
- CVE-2026-100863Heym versions 0.0.90 and earlier contain two server-side req…5
- CVE-2026-100864heym before 0.0.91 contains a sandbox escape vulnerability i…8.8
- CVE-2026-10087GitLab has remediated an issue in GitLab EE affecting all ve…8.7
- CVE-2026-10089The Insert Pages plugin for WordPress is vulnerable to Store…6.4
- CVE-2026-1009A stored cross-site scripting (XSS) vulnerability exists in …5.4
- CVE-2026-10090A flaw was found in the Application Subscription controller …9
- CVE-2026-10091The Email JavaScript Cloak plugin for WordPress is vulnerabl…7.2
- CVE-2026-10092The Cincopa video and media plug-in plugin for WordPress is …7.2
Are you affected by CVE-2026-100865?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
