CVE-2026-56269

MEDIUMPre-NVD 4.64.6
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-38746 (ENISA EUVD) · GHSA-m7mq-85xj-9x33 (GitHub Security Advisories)Source: ENISA EUVD

4.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Flowise before 3.1.0 (npm package flowise, versions 3.0.13 and earlier) uses a weak hardcoded default value 'Secre$t' for the TOKEN_HASH_SECRET environment variable in packages/server/src/enterprise/utils/tempTokenUtils.ts when the variable is not configured. This secret derives the AES-256-CBC key used to encrypt user IDs and workspace IDs in the 'meta' field of JWT tokens. An attacker who knows the default secret can decrypt this metadata to extract internal user and workspace identifiers, and re-encrypt manipulated values such as altered user or workspace IDs. Because the JWT signature is validated separately, decrypting or tampering with this metadata does not by itself grant access, but the disclosure of internal identifiers and possible metadata manipulation could aid privilege escalation or unauthorized data access.

CVSS v3
4.6
EG Score
4.6MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity46% × 45%
Impact severity (EG Severity): CVSS 4.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.1%
EPSS %ILE
2nd
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 (4.6): severity, escalated by confirmed exploitation. This CVE's 4.6 is its impact severity (EG Severity), not escalated.

EG Severity
4.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

April 16, 2026

Last Modified

October 25, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Patch available. Sources: github.
Web page

Flowise - Weak Default Token Hash Secret in JWT Token Encryption | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-weak-default-token-hash-secret-in-jwt-token-encryption
GitHub advisoryMentions a patch (unverified)

Weak Default Token Hash Secret · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-m7mq-85xj-9x33

Vendor Advisories for CVE-2026-56269(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
flowise—
  • every version up to 3.1.0: fixed in 3.1.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 132 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 32 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.1% · 2nd percentile
  2. 2026-10-29 16:35 UTCEG score recompute
  3. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-25 23:37 UTCEG score recompute
  7. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-25 14:18 UTCEG score recompute
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-22 21:11 UTCEG score recompute
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-18 03:29 UTCEG score recompute
  17. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-12 15:55 UTCEG score recompute
  24. 2026-10-11 19:38 UTCEG score recompute
  25. 2026-10-11 16:53 UTCEG score recompute
Show 75 more
  1. 2026-10-11 14:16 UTCEG score recompute
  2. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-10 19:25 UTCOSV refresh
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-09-21 06:49 UTCOSV refresh
  22. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-09-02 04:58 UTCOSV refresh
  35. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-08-23 00:19 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  43. 2026-08-21 23:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  44. 2026-08-20 22:55 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  45. 2026-08-19 17:04 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  46. 2026-08-17 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  47. 2026-08-16 14:56 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  48. 2026-08-16 06:34 UTCEG score recompute
  49. 2026-08-16 02:14 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  50. 2026-08-15 01:30 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  51. 2026-08-11 07:14 UTCEG score recompute
  52. 2026-08-11 00:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  53. 2026-08-10 05:35 UTCEG score recompute
  54. 2026-08-09 13:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  55. 2026-08-09 03:56 UTCEG score recompute
  56. 2026-08-08 16:37 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  57. 2026-08-07 13:22 UTCEG score recompute
  58. 2026-08-06 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  59. 2026-08-05 23:20 UTCEG score recompute
  60. 2026-08-05 19:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  61. 2026-08-04 15:10 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  62. 2026-08-04 10:39 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  63. 2026-08-03 21:32 UTCEG score recompute
  64. 2026-08-03 10:36 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  65. 2026-08-02 13:09 UTCEG score recompute
  66. 2026-08-01 04:16 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  67. 2026-07-30 19:20 UTCOSV refresh
  68. 2026-07-30 16:28 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  69. 2026-07-25 14:18 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  70. 2026-07-24 14:18 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  71. 2026-07-23 03:20 UTCEG score recompute▼ 1.00
  72. 2026-07-22 14:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  73. 2026-07-21 15:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  74. 2026-07-20 17:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  75. 2026-07-19 14:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-56269?
CVE-2026-56269 is a medium-severity vulnerability; its CVE record was published on April 16, 2026. Flowise before 3.1.0 (npm package flowise, versions 3.0.13 and earlier) uses a weak hardcoded default value 'Secre$t' for the TOKENHASHSECRET environment variable in packages/server/src/enterprise/utils/tempTokenUtils.ts when the variable is not configured. This secret derives the AES-256-CBC key…
When was CVE-2026-56269 made public?
CVE-2026-56269 was made public on April 15, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on April 16, 2026. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56269 actively exploited?
CVE-2026-56269 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56269?
CVE-2026-56269 has a CVSS base score of 4.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56269?
A fix for CVE-2026-56269 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56269 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-56269

Explore →

Is Your Infrastructure Affected by CVE-2026-56269?

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

Book a Demo →Browse All CVEs