VAITP Dataset

← Back to the dataset

CVE-2026-100865

Heym <0.0.53 evals workflow conditions via unsafe eval, allowing code execution.

  • CVSS 8.7
  • CWE-94
  • Design Defects
  • Remote

Heym before 0.0.53 evaluates workflow condition expressions using Python's eval() with insufficient sandboxing in the workflow executor service. Authenticated users can edit workflow condition nodes or import malicious templates to execute arbitrary Python and OS commands as the backend process user.

CVSS base score
8.7
Published
2026-09-27
OWASP
A03 Injection
Orthogonal defect classification
Checking
Code defect classification
Incorrect Check
Category
Design Defects
Subcategory
Poorly Designed Access Controls
Accessibility scope
Remote
Impact
Arbitrary Code Execution
Affected component
Python
Fixed by upgrading
Yes

Solution

Upgrade Heym to version 0.0.53 or later, which removes the unsafe eval() usage.

Vulnerable code sample

import json

class WorkflowExecutor:
    def __init__(self, workflow):
        self.workflow = workflow

    def evaluate_condition(self, node):
        # VULNERABLE: uses eval on user‑controlled expression
        expression = node.get('condition')
        return eval(expression, {"__builtins__": {}}, {})

    def run(self):
        for node in self.workflow['nodes']:
            if node['type'] == 'condition':
                if self.evaluate_condition(node):
                    self.execute(node['then'])
                else:
                    self.execute(node['else'])
            else:
                self.execute(node)

    def execute(self, action):
        # placeholder for action execution
        pass

Patched code sample

import json
import ast

class WorkflowExecutor:
    def __init__(self, workflow):
        self.workflow = workflow

    def evaluate_condition(self, node):
        # FIX: replace eval with safe literal evaluation
        expression = node.get('condition')
        try:
            # only allow simple boolean literals and logical operators
            tree = ast.parse(expression, mode='eval')
            for n in ast.walk(tree):
                if not isinstance(n, (ast.Expression, ast.BoolOp, ast.UnaryOp,
                                      ast.NameConstant, ast.Compare, ast.Load,
                                      ast.And, ast.Or, ast.Not, ast.Eq,
                                      ast.NotEq, ast.Lt, ast.LtE, ast.Gt,
                                      ast.GtE)):
                    raise ValueError("Unsafe expression")
            return eval(compile(tree, filename="<ast>", mode="eval"))
        except Exception:
            return False

    def run(self):
        for node in self.workflow['nodes']:
            if node['type'] == 'condition':
                if self.evaluate_condition(node):
                    self.execute(node['then'])
                else:
                    self.execute(node['else'])
            else:
                self.execute(node)

    def execute(self, action):
        # placeholder for action execution
        pass

Published fix

Public sources link this CVE to the changes below. The code samples above were generated to illustrate the defect; these links lead to the code the project actually changed.

  • Merge commit from fork (heymrun/heym)
    backend/app/api/oauth.py, backend/app/api/oauth.py · authorize_get, backend/app/api/oauth.py · authorize_post, backend/app/api/oauth.py · register_client, backend/app/api/slack.py · slack_webhook, backend/app/api/telegram.py · telegram_webhook, backend/app/services/workflow_executor.py · WorkflowExecutor._eval_substituted_python_expression

Cite this entry

@misc{vaitp:cve2026100865,
  title        = {{Heym <0.0.53 evals workflow conditions via unsafe eval, allowing code execution.}},
  author       = {Bogaerts, Fr\'ed\'eric and Ivaki, Naghmeh and Fonseca, Jos\'e},
  year         = {2026},
  note         = {VAITP Python Vulnerability Dataset, entry CVE-2026-100865},
  howpublished = {\url{https://netpack.pt/vaitp/vulnerability/CVE-2026-100865/}}
}

Download this entry as JSON Download the whole dataset

Introducing the "VAITP dataset": a specialized repository of Python vulnerabilities and patches, meticulously compiled for the use of the security research community. As Python's prominence grows, understanding and addressing potential security vulnerabilities become crucial. Crafted by and for the cybersecurity community, this dataset offers a valuable resource for researchers, analysts, and developers to analyze and mitigate the security risks associated with Python. Through the comprehensive exploration of vulnerabilities and corresponding patches, the VAITP dataset fosters a safer and more resilient Python ecosystem, encouraging collaborative advancements in programming security.

The supreme art of war is to subdue the enemy without fighting.

Sun Tzu – “The Art of War”

:: Shaping the future through research and ingenuity ::

Before you use the VAITP AI models

Please read and accept the following disclaimer:

By choosing "I understand and accept", you acknowledge that you understand and agree to these terms.