CVE-2026-47719

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. A secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-61208 (ENISA EUVD) · GHSA-w86f-rf9w-h3x6 (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.2, the DEVICE_WEBAPI_REQUEST and DEVICE_PROPERTY Socket.IO handlers in server/runtime/index.js omit isSocketWriteAuthorized and accept attacker-controlled property.address or endpoint connection data. A remote unauthenticated attacker can make server/runtime/devices/httprequest/index.js call axios.get against arbitrary HTTP or HTTPS destinations, connect to reachable OPC UA or ODBC services, and receive results through the corresponding Socket.IO event. This read SSRF oracle can expose cloud instance metadata, internal administrative services, industrial endpoints, and ODBC data reachable from the FUXA host, including when secureEnabled is true. This issue is fixed in version 1.3.2.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
68
EG Risk 68/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 8, 2026

Last Modified

October 22, 2026

Advisory Details (4)

Auto-updated Aug 18, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)

Unauthenticated SSRF via Socket.IO DEVICE_WEBAPI_REQUEST and DEVICE_PROPERTY with response reading · Advisory · frangoteam/FUXA · GitHub

https://github.com/frangoteam/FUXA/security/advisories/GHSA-w86f-rf9w-h3x6
GitHub release Patch Available

v1.3.2

Patch available: frangoteam/FUXA v1.3.2

https://github.com/frangoteam/FUXA/releases/tag/v1.3.2
GitHub pull request Patch Available

Fix unauthenticated Socket.IO SSRF paths

Patch available: frangoteam/FUXA v1.3.2 (PR #2344 merged 2026-05-03)

https://github.com/frangoteam/FUXA/pull/2344
GitHub commit Patch Available

commit 7b2088eaae2b (frangoteam/FUXA)

Patch available: frangoteam/FUXA v1.3.2 (contains commit 7b2088eaae2b)

https://github.com/frangoteam/FUXA/commit/7b2088eaae2be318d962dcba34bfc7a7f26837bd

Vendor Advisories for CVE-2026-47719(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmfuxa-server—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
fuxa-server—
  • every version through 1.1.14-1243: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 205 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-30 03:00 UTCEG score recompute
  3. 2026-10-30 03:00 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-10-25 14:24 UTCEG score recompute
  10. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-10-22 22:26 UTCEG score recompute
  13. 2026-10-22 22:26 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-10-18 03:35 UTCEG score recompute
  20. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-17 12:39 UTCEG score recompute
  22. 2026-10-17 12:38 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
Show 75 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-12 16:01 UTCEG score recompute
  4. 2026-10-11 19:44 UTCEG score recompute
  5. 2026-10-11 16:59 UTCEG score recompute
  6. 2026-10-11 14:23 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-10-03 10:09 UTCOSV refresh
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  21. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  27. 2026-09-14 04:47 UTCEG score recompute
  28. 2026-09-14 04:47 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  29. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  30. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  31. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-09-09 23:00 UTCEG score recompute
  33. 2026-09-09 23:00 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  34. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  36. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  40. 2026-08-31 01:31 UTCEG score recompute
  41. 2026-08-31 01:31 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  42. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  43. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  46. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  47. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  48. 2026-08-25 01:12 UTCEG score recompute
  49. 2026-08-25 01:12 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  50. 2026-08-23 23:45 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  51. 2026-08-23 11:36 UTCEG score recompute
  52. 2026-08-23 11:36 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  53. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  54. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  55. 2026-08-21 20:24 UTCEG score recompute
  56. 2026-08-21 20:24 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  57. 2026-08-21 19:20 UTCEG score recompute
  58. 2026-08-21 19:20 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  59. 2026-08-21 07:56 UTCEG score recompute
  60. 2026-08-21 07:56 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  61. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  62. 2026-08-20 20:54 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  63. 2026-08-20 09:26 UTCEG score recompute
  64. 2026-08-20 09:26 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  65. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  66. 2026-08-18 20:25 UTCEG score recompute
  67. 2026-08-18 20:25 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  68. 2026-08-18 20:12 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  69. 2026-08-17 12:46 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  70. 2026-08-17 01:43 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  71. 2026-08-16 12:01 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  72. 2026-08-16 00:59 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  73. 2026-08-15 11:45 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  74. 2026-08-14 20:32 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2
  75. 2026-08-14 09:29 UTCGHSA enrichmentGHSA-w86f-rf9w-h3x6 · GitHub severity HIGH · GitHub CVSS 8.2

Frequently asked(5)

What is CVE-2026-47719?
CVE-2026-47719 is a high-severity vulnerability; its CVE record was published on June 8, 2026. FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.2, the DEVICEWEBAPIREQUEST and DEVICE_PROPERTY Socket.IO handlers in server/runtime/index.js omit isSocketWriteAuthorized and accept attacker-controlled property.address or endpoint connection data. A remote…
When was the CVE record for CVE-2026-47719 published?
The CVE record for CVE-2026-47719 was published on June 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-47719 actively exploited?
CVE-2026-47719 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47719?
CVE-2026-47719 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47719?
A fix for CVE-2026-47719 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47719 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47719

Explore →

Is Your Infrastructure Affected by CVE-2026-47719?

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