CVE-2026-84207

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-09-01. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 8, 2026

Advisory Details (7)

Auto-updated Sep 1, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
generic

Heym before 0.0.98 SSRF via WebSocket endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/heym-before-0.0.98-ssrf-via-websocket-endpoints
generic

heym/backend/app/services/websocket_trigger_service.py at v0.0.97 · heymrun/heym · GitHub

https://github.com/heymrun/heym/blob/v0.0.97/backend/app/services/websocket_trigger_service.py
generic

heym/backend/app/services/websocket_utils.py at v0.0.97 · heymrun/heym · GitHub

https://github.com/heymrun/heym/blob/v0.0.97/backend/app/services/websocket_utils.py
github_release Patch Available

v0.0.98

Patch available: heymrun/heym v0.0.98

https://github.com/heymrun/heym/releases/tag/v0.0.98
github_commit Patch Available

commit 540aade7c749 (heymrun/heym)

Patch available: heymrun/heym v0.0.98 (contains commit 540aade7c749)

https://github.com/heymrun/heym/commit/540aade7c7495295062f32f4dfd0d6805f066f0c
github Patch Available🟡 PoC Available

Server-Side Request Forgery (SSRF) in both WebSocket egress paths: the egress guard covers http(s) only and neither the Send node nor the Trigger calls it · Advisory · heymrun/heym · GitHub

https://github.com/heymrun/heym/security/advisories/GHSA-mqw6-g845-w596
generic

GitHub - heymrun/heym: Build agentic systems. Run them with confidence. Orchestrate agents, automate business processes, inspect every execution, and keep humans in control. Deploy Heym on your own infrastructure. · GitHub

https://github.com/heymrun/heym

Vendor Advisories for CVE-2026-84207(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:29 UTCEG score recompute
  2. 2026-09-20 20:29 UTCGHSA enrichment
  3. 2026-09-20 20:16 UTCEPSS rescore
  4. 2026-09-19 20:57 UTCEG score recompute
  5. 2026-09-19 20:57 UTCGHSA enrichment
  6. 2026-09-18 21:25 UTCEG score recompute
  7. 2026-09-18 21:25 UTCGHSA enrichment
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-17 20:54 UTCEG score recompute
  10. 2026-09-17 20:54 UTCGHSA enrichment
  11. 2026-09-17 19:32 UTCEPSS rescore
  12. 2026-09-16 21:22 UTCEG score recompute
  13. 2026-09-16 21:22 UTCGHSA enrichment
  14. 2026-09-16 14:09 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 21:27 UTCEG score recompute
  17. 2026-09-15 21:27 UTCGHSA enrichment
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 21:55 UTCGHSA enrichment
  21. 2026-09-13 22:22 UTCEG score recompute
  22. 2026-09-13 22:22 UTCGHSA enrichment
  23. 2026-09-12 22:50 UTCEG score recompute
  24. 2026-09-12 22:50 UTCGHSA enrichment
  25. 2026-09-11 23:18 UTCEG score recompute
Show 29 more
  1. 2026-09-11 23:18 UTCGHSA enrichment
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-10 23:09 UTCEG score recompute
  5. 2026-09-10 23:09 UTCGHSA enrichment
  6. 2026-09-09 23:37 UTCEG score recompute
  7. 2026-09-09 23:37 UTCGHSA enrichment
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-08 20:50 UTCGHSA enrichment
  10. 2026-09-07 17:50 UTCEG score recompute
  11. 2026-09-07 17:50 UTCGHSA enrichment
  12. 2026-09-06 18:18 UTCEG score recompute
  13. 2026-09-06 18:18 UTCGHSA enrichment
  14. 2026-09-06 13:48 UTCEPSS rescore
  15. 2026-09-05 18:45 UTCEG score recompute
  16. 2026-09-05 18:45 UTCGHSA enrichment
  17. 2026-09-05 15:31 UTCEPSS rescore
  18. 2026-09-04 19:13 UTCEG score recompute
  19. 2026-09-04 19:13 UTCGHSA enrichment
  20. 2026-09-04 05:07 UTCEPSS rescore
  21. 2026-09-03 19:40 UTCGHSA enrichment
  22. 2026-09-02 20:00 UTCEG score recompute
  23. 2026-09-02 20:00 UTCGHSA enrichment
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 18:24 UTCEG score recompute
  26. 2026-09-01 17:42 UTCEG score recompute
  27. 2026-09-01 16:25 UTCEG score recompute
  28. 2026-09-01 15:44 UTCEG score recompute
  29. 2026-09-01 15:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84207?
CVE-2026-84207 is a medium vulnerability published on September 1, 2026. 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…
When was CVE-2026-84207 disclosed?
CVE-2026-84207 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84207 actively exploited?
CVE-2026-84207 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.8% of all scored CVEs.
What is the CVSS score of CVE-2026-84207?
CVE-2026-84207 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-84207?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84207, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-84207

Explore →

Is Your Infrastructure Affected by CVE-2026-84207?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs