CVE-2026-67545: Heym: Server-Side Request Forgery (SSRF) in HTTP Workflow Node
Heym builds and runs agentic systems and business-process automations on self-hosted infrastructure. Prior to version 0.0.73, the HTTP workflow node in Heym makes outbound HTTP requests to user-supplied URLs without validation of the target host or IP address. If a workflow author has already configured an HTTP node that targets internal addresses such as cloud metadata endpoints or private network hosts, and exposed the workflow with anonymous execution, an unauthenticated attacker can trigger the preconfigured SSRF sink. The same project has comprehensive SSRF protection in its MCP integration, which is absent from the HTTP node. This issue has been patched in version 0.0.73.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Heymto a version that resolves this vulnerability.Fixed in 0.0.73
Event History
Frequently Asked Questions
Which deployments are realistically exposed to unauthenticated exploitation?
Deployments prior to 0.0.73 are exposed when a workflow author has configured an HTTP workflow node to reach an internal target, such as a private-network host or cloud metadata endpoint, and has enabled anonymous execution for that workflow.
What does an attacker need to exploit this issue?
The attacker does not need authentication or user interaction, but they need access to an anonymously executable workflow that already contains a vulnerable, preconfigured HTTP node. The issue does not state that an attacker can supply or change the target URL themselves.
How can teams tell whether they are affected?
Check whether the Heym version is earlier than 0.0.73, then review HTTP workflow nodes for URLs resolving to internal addresses, including cloud metadata endpoints and private hosts. Also identify whether any workflows containing those nodes permit anonymous execution.
What should be done if an immediate upgrade is not possible?
Disable anonymous execution for workflows containing HTTP nodes, or remove or reconfigure HTTP nodes that target internal addresses. Upgrade to version 0.0.73 when possible, as that version contains the patch.