Description
heym before 0.0.109 contains a server-side request forgery vulnerability in the Slack, Discord, and Crawler workflow nodes. These nodes issue HTTP requests to URLs taken from user-created credentials (webhook_url / flaresolverr_url) using an unguarded HTTP client, bypassing the SSRF egress guard that already protects the HTTP, WebSocket, and MCP nodes; the credential API validates only that the URL is non-empty. Any registered user can create a credential pointing at an internal address and execute a workflow, causing the backend to reach loopback, private, link-local, or cloud-metadata endpoints and return the full response body in the node output (non-blind SSRF).
Published: 2026-09-27
Score: 7.6 High
EPSS: n/a
KEV: No
Impact: Server‑Side Request Forgery allowing attacker access to internal resources
Action: Immediate Patch
AI Analysis

Impact

heym prior to version 0.0.109 contains an SSRF flaw in its Slack, Discord, and Crawler workflow nodes. The nodes build HTTP requests to URLs taken from user‑created credentials without validating the target address, beyond checking that the URL string is non‑empty. An attacker can supply a webhook or flaresolverr URL that points to a private, loopback, link‑local, or cloud‑metadata location. The backend process then retrieves the full response body and returns it in the node output, giving the attacker non‑blind access to sensitive internal data and services.

Affected Systems

Any instance of the heym application running a version earlier than 0.0.109 is vulnerable. The flaw is present in the Slack, Discord, and Crawler nodes and can be exploited by any registered user who can create or modify credentials. The only vendor/product affected is heymrun:heym.

Risk and Exploitability

The CVSS base score of 7.6 indicates a high‑severity vulnerability. No EPSS score is available and the issue is not listed in the CISA KEV catalog. Exploitation requires a registered account; the attacker crafts a credential that points to an internal endpoint and triggers a workflow. Because the backend returns the full response body, a single user can probe cloud‑metadata services or other internal systems and exfiltrate information, posing a significant risk to environments exposed via the heym service.

Generated by OpenCVE AI on September 27, 2026 at 03:57 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the heym application to version 0.0.109 or later to remove the SSRF capability in the affected nodes.
  • If an immediate upgrade is not possible, temporarily disable or modify any credential URLs used by the Slack, Discord, and Crawler nodes so that they do not point to private, loopback, link‑local, or cloud‑metadata addresses, and delete stored credentials that target such addresses.
  • Implement or tighten network egress controls on the backend to block outbound traffic to private, loopback, link‑local, or cloud‑metadata IP ranges, or monitor outgoing HTTP requests for suspicious internal destinations to prevent data exfiltration.

Generated by OpenCVE AI on September 27, 2026 at 03:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 27 Sep 2026 04:30:00 +0000

Type Values Removed Values Added
First Time appeared Heymrun
Heymrun heym
Vendors & Products Heymrun
Heymrun heym

Sun, 27 Sep 2026 02:00:00 +0000

Type Values Removed Values Added
Description heym before 0.0.109 contains a server-side request forgery vulnerability in the Slack, Discord, and Crawler workflow nodes. These nodes issue HTTP requests to URLs taken from user-created credentials (webhook_url / flaresolverr_url) using an unguarded HTTP client, bypassing the SSRF egress guard that already protects the HTTP, WebSocket, and MCP nodes; the credential API validates only that the URL is non-empty. Any registered user can create a credential pointing at an internal address and execute a workflow, causing the backend to reach loopback, private, link-local, or cloud-metadata endpoints and return the full response body in the node output (non-blind SSRF).
Title heym before 0.0.109 Server-Side Request Forgery via Workflow Nodes
Weaknesses CWE-918
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 7.6, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-27T01:28:49.185Z

Reserved: 2026-09-27T00:20:03.854Z

Link: CVE-2026-100858

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-27T02:17:25.340

Modified: 2026-09-27T02:17:25.340

Link: CVE-2026-100858

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-27T04:15:08Z

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)