Quick answers
- Is CVE-2026-84207 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84207 being exploited in the wild.
- How severe is CVE-2026-84207?
- Medium severity, with a CVSS score of 5.4, published 1 September 2026.
- Which products and versions are affected?
- Heym Heym before 0.0.98.
- Is there a fix for CVE-2026-84207?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-84207 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-84207?
- Check whether anything you run is named in the advisory. 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
This is a Server-Side Request Forgery (SSRF) vulnerability caused by insufficient egress validation on WebSocket workflow nodes. The vulnerable WebSocket Send and WebSocket Trigger nodes fail to apply security guards that restrict outbound connections to internal services. An authenticated attacker can craft workflow nodes with arbitrary URLs and custom headers to bypass network policy controls and connect to internal resources (databases, metadata services, internal APIs) that should be inaccessible. The WebSocket Trigger node can additionally read and exfiltrate response data. This vulnerability requires authentication and access to the workflow builder interface. The fix is available in version 0.0.98 and later.
Affected products
- Heym Heym before 0.0.98
Timeline
- 2026-09-01: disclosed