CVE-2026-84207: Heym before 0.0.98 SSRF via WebSocket endpoints
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: heymrun heym 0.0.98.
Low priority for now. Upgrade to heymrun heym 0.0.98 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Heym before 0.0.98 fails to apply SSRF egress guards to WebSocket Send and WebSocket Trigger nodes, allowing authenticated users to connect to internal services. Attackers can craft workflow nodes with arbitrary URLs and headers to reach internal services and read responses from the WebSocket Trigger node.
- Published
- Sep 1, 2026
- Updated
- Sep 8, 2026
- EPSS
- 0.3% · 28th percentile
- CWE
- CWE-918
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
heymrun heym
- 0.0.98not affected
- before 0.0.98affected · semver
Same product
heymrun: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-55376heym Python Tool Sandbox Escape35Monitor
- CVE-2026-100865Heym before 0.0.53 Remote Code Execution via eval() Sandbox Escape34Monitor
- CVE-2026-100864heym before 0.0.91 Remote Code Execution via Expression Engine34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-45226May 12, 2026 · Heym < 0.0.21 Authorization Bypass in Workflow Execution30Monitor
- ← EarlierCVE-2026-45227May 12, 2026 · Heym < 0.0.21 Sandbox Escape via Python Introspection34Monitor
- Later →CVE-2026-100858Sep 27, 2026 · heym before 0.0.109 Server-Side Request Forgery via Workflow Nodes30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| heymrun heym | 0.0.98 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- euriconicaciofinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-10085826 days apartheym before 0.0.109 Server-Side Request Forgery via Workflow Nodes30Monitor
- CVE-2026-10085926 days apartHeym before 0.0.106 Credential Exfiltration via URL Override28Monitor
- CVE-2026-10086126 days apartheym before 0.0.105 SSRF via credential-controlled base URLs21Monitor
- CVE-2026-10086326 days apartHeym before 0.0.91 SSRF via image fetching and IPv6 validation21Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.com/heymrun/heym/blob/v0.0.97/backend/app/services/websocket_trigger_service.py
- github.com/heymrun/heym/blob/v0.0.97/backend/app/services/websocket_utils.py
- github.com/heymrun/heym/commit/540aade7c7495295062f32f4dfd0d6805f066f0c
- github.com/heymrun/heym/releases/tag/v0.0.98
- github.com/heymrun/heym/security/advisories/GHSA-mqw6-g845-w596
- www.vulncheck.com/advisories/heym-before-0.0.98-ssrf-via-websocket-endpoints
Vendor advisories and official records. Exploit/PoC links are deliberately left out.