CVE-2026-41277

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 44% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, a Mass Assignment vulnerability in the DocumentStore creation endpoint allows authenticated users to control the primary key (id) and internal state fields of DocumentStore entities. Because the service uses repository.save() with a client-supplied primary key, the POST create endpoint behaves as an implicit UPSERT operation. This enables overwriting existing DocumentStore objects. In multi-workspace or multi-tenant deployments, this can lead to cross-workspace object takeover and broken object-level authorization (IDOR), allowing an attacker to reassign or modify DocumentStore objects belonging to other workspaces. This vulnerability is fixed in 3.1.0.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
25.5%
KEV
Not listed

Published

April 23, 2026

Last Modified

April 25, 2026

Advisory Details (1)

Auto-updated May 2, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Mass Assignment in DocumentStore Create Endpoint Leads to Cross-Workspace Object Takeover (IDOR) · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-3prp-9gf7-4rxx

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
flowise—3.1.0—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 106 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41277?
CVE-2026-41277 is a high vulnerability published on April 23, 2026. Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, a Mass Assignment vulnerability in the DocumentStore creation endpoint allows authenticated users to control the primary key (id) and internal state fields of DocumentStore entities. Because the…
When was CVE-2026-41277 disclosed?
CVE-2026-41277 was first published in the National Vulnerability Database on April 23, 2026, with the most recent update on April 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41277 actively exploited?
CVE-2026-41277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41277?
CVE-2026-41277 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-41277?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41277, 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-41277

Explore →

Is Your Infrastructure Affected by CVE-2026-41277?

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

Start Free Scan →Browse All CVEs