# CVE-2026-100858: heym server-side request forgery in workflow nodes

Source: https://junglewise.ai/threats/cve-2026-100858-heym-before-0-0-109-contains-a-server-side-request-forgery  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-27. Updated: 2026-09-27  
License: CC BY 4.0 with a link back

CVE-2026-100858 · Severity: medium · CVSS 6.8 · Published 2026-09-27

heym is a workflow automation platform that allows users to create workflows with Slack, Discord, and web crawler nodes. A server-side request forgery vulnerability allows any registered user to make the backend reach internal network addresses and cloud metadata endpoints by crafting malicious credentials, potentially exposing sensitive configuration, API responses, and cloud metadata that could lead to further compromise.

Technologies: [Heymrun Heym](https://junglewise.ai/threats/technologies/heym). Vendors: [Heymrun](https://junglewise.ai/threats/vendors/heymrun).

## Quick answers

**Is CVE-2026-100858 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-100858 being exploited in the wild.

**How severe is CVE-2026-100858?** Medium severity, with a CVSS score of 6.8, published 27 September 2026.

**Which products and versions are affected?** Heymrun Heym before 0.0.109.

**Is there a fix for CVE-2026-100858?** A patch was published on 2026-09-27: version 0.0.109 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-100858 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-100858?** Check whether you run Heymrun Heym at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The Slack, Discord, and Crawler workflow nodes accept URLs from user-created credentials (webhook_url and flaresolverr_url) and issue HTTP requests via an unguarded HTTP client, bypassing the SSRF guard that protects other nodes. The vulnerability is non-blind SSRF: the full response body is returned in node output. Exploitation requires user registration and workflow execution permissions, with no additional complexity beyond crafting a credential pointing to loopback (127.0.0.1), private subnets, link-local addresses, or cloud metadata endpoints.

## Affected products

- heymrun heym before 0.0.109

## Timeline

- 2026-09-12: disclosed
- 2026-09-27: patched: version 0.0.109

## References

- [https://github.com/heymrun/heym/security/advisories/GHSA-39j3-6x3x-8rcr](https://github.com/heymrun/heym/security/advisories/GHSA-39j3-6x3x-8rcr)
- [https://www.vulncheck.com/advisories/heym-before-0.0.109-server-side-request-forgery-via-workflow-nodes](https://www.vulncheck.com/advisories/heym-before-0.0.109-server-side-request-forgery-via-workflow-nodes)

## Related threats

- [Heym privilege escalation via error_workflow_id field](https://junglewise.ai/threats/cve-2026-110873-heym-from-0-0-55-before-0-0-121-contains-a-privilege-escalation)
- [Heym token leakage in HITL review links via header spoofing](https://junglewise.ai/threats/cve-2026-105396-heym-before-v0-0-112-contains-a-token-leakage-vulnerability-in)
- [Heym Telegram webhook auth bypass](https://junglewise.ai/threats/cve-2026-101050-heym-before-0-0-53-fails-to-verify-the-x-telegram-bot-api-secret)
- [Heym authentication bypass in Slack webhook verification](https://junglewise.ai/threats/cve-2026-101049-heym-before-0-0-53-fails-to-verify-slack-request-signatures-when)
- [Heym multiple RCE and authentication bypass vulnerabilities](https://junglewise.ai/threats/cve-2026-100865-heym-before-0-0-53-contains-multiple-independent-vulnerabilities)
