PULSE
FEED
ransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerceransomsilentransomgroup reclama a Kutak Rock LLP · US · Professional Servicesransomincransom reclama a CHAMBOURCY · FR · Government & Defenseransomhandsome boy hacking club reclama a UCHealth · US · Healthcareransomhandsome boy hacking club reclama a Smith & Wesson · US · Manufacturingransomdeadlock reclama a MedMira Inc · CA · Healthcareransomrhysida reclama a Rober & Phillipsransomsoulgroup reclama a SHOPBOT TOOLS, INC. · US · Retail & E-Commerceransomsoulgroup reclama a Noble Inc. · US · Energy & Utilitiesransomsoulgroup reclama a United Medical Doctors · US · Healthcareransomsoulgroup reclama a METO Systems · US · Technologyransomsoulgroup reclama a Nephrology Associates · US · Healthcareransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerceransomsilentransomgroup reclama a Kutak Rock LLP · US · Professional Servicesransomincransom reclama a CHAMBOURCY · FR · Government & Defenseransomhandsome boy hacking club reclama a UCHealth · US · Healthcareransomhandsome boy hacking club reclama a Smith & Wesson · US · Manufacturingransomdeadlock reclama a MedMira Inc · CA · Healthcareransomrhysida reclama a Rober & Phillipsransomsoulgroup reclama a SHOPBOT TOOLS, INC. · US · Retail & E-Commerceransomsoulgroup reclama a Noble Inc. · US · Energy & Utilitiesransomsoulgroup reclama a United Medical Doctors · US · Healthcareransomsoulgroup reclama a METO Systems · US · Technologyransomsoulgroup reclama a Nephrology Associates · US · Healthcare
← All CVEs
CVE WatchOct 26, 2026

CVE-2026-41277

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

CVSS

8.8

High

EPSS

3.1%

p88

KEV

—

Exploit Today

26

0-100

Published: Apr 23, 2026 · Last modified: Oct 26, 2026 · CWE-284 · CWE-639 · CWE-915

EPSS · 30d
0.5%EPSS · 30 days3.1%
2026-10-222026-11-18
Technical description

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.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-163194.3 MED
—
———IBM API Connect 10.0.8.0 through 10.0.8.13 could allow a remote authenticated attacker to delete API keys belonging to other users due to improper authorization checks.6h
CVE-2026-148854.8 MED
—
———IBM watsonx.data 2.4.0 through 2.4.0 patch 8 could allow a remote attacker to obtain sensitive information due to improper access control.6h
CVE-2026-148805.3 MED
—
———IBM watsonx.data 2.4.0 through 2.4.0 patch 8 could allow unauthorized network access due to insufficient network segmentation controls.6h
CVE-2026-1313048.1 HIG
—
———In Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles could access data associated with another tenant and cause actions to be attributed to that tenant through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a request.6h
CVE-2026-1312978.1 HIG
—
———In Splunk SOAR versions below 8.8.0, an operator of a configured identity provider could authenticate as an existing user associated with another configured identity provider. If that account has the "Administrator" Splunk SOAR role, the operator could control the Splunk SOAR deployment. Splunk SOAR does not bind external user accounts to the identity provider that provisions them and authenticates accounts by username without verifying provider ownership. The vulnerability requires more than one configured external identity provider with distinct trust domains and a target username that an operator of a configured identity provider can authenticate through a different provider. For more information see Configure single sign-on authentication (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.7.0/manage-your-splunk-soar-on-premises-users-and-accounts/configure-single-sign-on-authentication-for-splunk-soar-on-premises) and Manage roles and permissions (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.7h
CVE-2026-1312946.5 MED
—
———In Splunk SOAR versions below 8.8.0, an authenticated user who can edit and run playbooks on a container label could associate a custom-function callback with another playbook run. The callback could modify the state of a container outside the authorized scope for that user. The vulnerability is possible because Splunk SOAR does not bind playbook API requests to the trusted playbook run and container context.6h