CVE-2026-46442

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 36% (98th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-35110 (ENISA EUVD) · GHSA-9rvc-vf7m-pgm2 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
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: 36%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.1.2, POST /api/v1/node-custom-function lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the Custom JS Function node. When E2B_APIKEY is not configured — the common deployment case — Flowise executes this code inside a NodeVM sandbox. This sandbox can be escaped, allowing an attacker to reach the host process object and execute system commands via child_process. The result is authenticated remote code execution on the Flowise server host. This issue has been patched in version 3.1.2.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
36%
EPSS %ILE
98th
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
36% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

July 23, 2026

Advisory Details (2)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Authenticated Host RCE via POST /api/v1/node-custom-function and NodeVM Sandbox Escape · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-9rvc-vf7m-pgm2
GitHub release Patch Available

flowise@3.1.2

Patch available: FlowiseAI/Flowise flowise@3.1.2

https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.1.2

Vendor Advisories for CVE-2026-46442(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
npmflowise @ 3.1.2 (fixes <= 3.1.1)—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
flowise—
  • every version up to 3.1.2: fixed in 3.1.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 56× 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 198 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 98 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-46442.yaml
    Published Jul 21, 2026

    Flowise < 3.1.2 - node-custom-function Unauthorized RCE

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46442?
CVE-2026-46442 is a critical-severity vulnerability; its CVE record was published on June 8, 2026. Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.1.2, POST /api/v1/node-custom-function lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the Custom JS Function node. When…
When was the CVE record for CVE-2026-46442 published?
The CVE record for CVE-2026-46442 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 July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-46442 actively exploited?
CVE-2026-46442 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46442?
CVE-2026-46442 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-46442?
A fix for CVE-2026-46442 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46442 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-46442

Explore →

Is Your Infrastructure Affected by CVE-2026-46442?

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

Book a Demo →Browse All CVEs