GHSA-8wj7-v2w6-wfcx: 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
Who can exploit this issue?
An unauthenticated attacker can exploit it only when a workflow containing an HTTP node has been exposed for anonymous execution and that node is already configured to request an internal or otherwise sensitive target.
Does an attacker need to create or edit a workflow to exploit it?
No. The described attack triggers a preconfigured HTTP workflow node; the attacker does not need workflow-author permissions if anonymous execution is enabled.
Which deployments are affected?
Heym versions before 0.0.73 are affected where HTTP workflow nodes can make requests to user-supplied URLs without target host or IP validation. Deployments without anonymously executable workflows containing such HTTP nodes are not described as exposed to unauthenticated triggering.
What should be done if an immediate upgrade is not possible?
Disable anonymous execution for workflows that contain HTTP nodes, or remove or change HTTP-node targets that point to private network hosts or cloud metadata endpoints. Review existing HTTP-node configurations for internal-address targets.
How can I determine whether I may already be exposed?
Identify Heym instances running a version earlier than 0.0.73, then review workflows exposed to anonymous execution. Check whether their HTTP nodes are configured with URLs that resolve to private network services, cloud metadata endpoints, or other internal targets.