CVE
Heym: Server-Side Request Forgery (SSRF) in HTTP Workflow Node
Affects Heym workflows that contain an HTTP node targeting internal addresses and are exposed with anonymous execution. Fixed in Heym 0.0.73.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.0.73
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.0.73.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Heym, an automation platform, has a flaw in its HTTP workflow node that lets an unauthenticated attacker over the network make requests to internal addresses, such as cloud metadata endpoints or private hosts, but only when a workflow author has already pointed the node at such a target and the workflow is exposed with anonymous execution. The attack is not easy to carry out, and the issue is fixed in a later release.
Read the original description
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.
Who should check
Operators of self-hosted Heym (heymrun/heym) at or before 0.0.73 that run HTTP workflow nodes with anonymous workflow execution enabled
Read the source excerpt
“If a workflow author has already configured an HTTP node that targets internal addresses such as cloud metadata endpoints or private network hosts”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.4/10CVSS 7.4
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.0.73.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-67545 (Heym: Server-Side Request Forgery (SSRF) in HTTP Workflow Node), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-67545 (entry last updated 2026-11-11):
Affected:
- heymrun heym: fixed in 0.0.73
Fixed versions: 0.0.73.
Conditions (all must be true for the bug to be hit):
- A workflow author has configured an HTTP node that targets internal addresses such as cloud metadata endpoints or private network hosts (source: https://github.com/heymrun/heym/security/advisories/GHSA-8wj7-v2w6-wfcx)
- The workflow is exposed with anonymous execution (source: https://github.com/heymrun/heym/security/advisories/GHSA-8wj7-v2w6-wfcx)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-67545 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-67545 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/heymrun/heym/security/advisories/GHSA-8wj7-v2w6-wfcx
- https://github.com/heymrun/heym/commit/360a8de56ab9be0b11acdfe89168c5f2d7ab6b1e
- https://github.com/heymrun/heym/commit/583311603f8f81bf2f45a842727046ef17c99c9e
- https://github.com/heymrun/heym/commit/87c216f6e564c58d1dd747115d079fb487233ccf
- https://github.com/heymrun/heym/releases/tag/0.0.73
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-67545
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-67545"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- heymrun heym
fixed in 0.0.73
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-67545
Is CVE-2026-67545 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The HTTP workflow node can make the Heym backend send requests to localhost, private-network, link-local, or cloud metadata HTTP(S) endpoints. This may expose internal HTTP services or cloud metadata responses.Source: github.com
Which versions are affected by CVE-2026-67545?
heym: before 0.0.73.Source: cve.now feed data
Am I affected, and how do I check?
Heym versions before 0.0.73 are affected, and only where a workflow has an HTTP node that targets internal addresses such as cloud metadata endpoints or private network hosts and the workflow is exposed with anonymous execution. To check, look at the installed Heym version and at whether any anonymous-execution workflow includes such an HTTP node.Source: github.com
How do I fix CVE-2026-67545?
Upgrade Heym to version 0.0.73 or later, which contains the patch.Source: github.com