heymrun Heym up to 0.0.72 HTTP workflow node server-side request forgery

Summaryinfo

A vulnerability, which was classified as critical, has been found in heymrun Heym up to 0.0.72. This impacts an unknown function of the component HTTP workflow node. The manipulation leads to server-side request forgery. This vulnerability is referenced as CVE-2026-67545. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in heymrun Heym up to 0.0.72. This issue affects an unknown functionality of the component HTTP workflow node. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-67545 since 07/29/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 0.0.73 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• heymrun

Name

• Heym

Version

• 0.0.1
• 0.0.2
• 0.0.3
• 0.0.4
• 0.0.5
• 0.0.6
• 0.0.7
• 0.0.8
• 0.0.9
• 0.0.10
• 0.0.11
• 0.0.12
• 0.0.13
• 0.0.14
• 0.0.15
• 0.0.16
• 0.0.17
• 0.0.18
• 0.0.19
• 0.0.20
• 0.0.21
• 0.0.22
• 0.0.23
• 0.0.24
• 0.0.25
• 0.0.26
• 0.0.27
• 0.0.28
• 0.0.29
• 0.0.30
• 0.0.31
• 0.0.32
• 0.0.33
• 0.0.34
• 0.0.35
• 0.0.36
• 0.0.37
• 0.0.38
• 0.0.39
• 0.0.40
• 0.0.41
• 0.0.42
• 0.0.43
• 0.0.44
• 0.0.45
• 0.0.46
• 0.0.47
• 0.0.48
• 0.0.49
• 0.0.50
• 0.0.51
• 0.0.52
• 0.0.53
• 0.0.54
• 0.0.55
• 0.0.56
• 0.0.57
• 0.0.58
• 0.0.59
• 0.0.60
• 0.0.61
• 0.0.62
• 0.0.63
• 0.0.64
• 0.0.65
• 0.0.66
• 0.0.67
• 0.0.68
• 0.0.69
• 0.0.70
• 0.0.71
• 0.0.72

Website

• Product: https://github.com/heymrun/heym/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion