HEYM · CVE-2026-67545 · Other
NO FIX YET · SEE WHAT TO DO
Heym's HTTP workflow node sends requests to user-supplied URLs without checking the target host or IP address. If a workflow author has pointed an HTTP node at internal addresses such as cloud metadata endpoints and the workflow allows anonymous execution, an unauthenticated attacker can trigger those requests and reach internal services.
first public Jul 19, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Self-hosted Heym deployments are exposed when a workflow has an HTTP node that targets internal addresses and that workflow is exposed with anonymous execution. An attacker with no account can trigger the preconfigured request. Teams running Heym as a managed service or without anonymous workflow execution are less exposed, and any team on 0.0.73 or later is covered.
Not affected if anonymous-execution-disabled, heym-0.0.73-or-later, no-internal-http-targets
Who cares heym, self-hosted, ssrf, workflow-automation
Unknown from the sources.
0.0.73 or later.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.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.