CVE-2026-56278

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-01. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

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

Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses a weak hardcoded default secret ('flowise') for the express-session middleware when the EXPRESS_SESSION_SECRET environment variable is not set (packages/server/src/enterprise/middleware/passport/index.ts). Because this default secret is publicly visible in the source code, an attacker can forge valid signed session cookies to impersonate any user and bypass authentication.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
28.5%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 1, 2026
Patch available. Sources: github.
generic

Flowise - Session Hijacking via Weak Default Express Session Secret | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-session-hijacking-via-weak-default-express-session-secret
github Patch Available

Weak Default Express Session Secret · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-2qqc-p94c-hxwh

Vendor Advisories for CVE-2026-56278(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 rangeFixed inDependents
flowise—3.1.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 131× 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.

Showing the most recent 100 of 131 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56278?
CVE-2026-56278 is a critical vulnerability published on July 1, 2026. Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses a weak hardcoded default secret ('flowise') for the express-session middleware when the EXPRESSSESSIONSECRET environment variable is not set (packages/server/src/enterprise/middleware/passport/index.ts). Because this default secret is…
When was CVE-2026-56278 disclosed?
CVE-2026-56278 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56278 actively exploited?
CVE-2026-56278 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56278?
CVE-2026-56278 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-56278?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56278, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56278?

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

Start Free Scan →Browse All CVEs