Flowise: Improperly Controlled Modification of Dynamically-Determined Object Attributes
CVE-2026-30822 is a high-severity improperly controlled modification of dynamically-determined object attributes vulnerability in Flowise from FlowiseAI, with a CVSS 3.0 base score of 7.7 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Flowise versions: < 3.0.13. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 15% chance of exploitation within 30 days, which is in the top 3.23% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Check which version of Flowise you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L. Scored by CNA (github.com).
Official description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.0.13, unauthenticated users can inject arbitrary values into internal database fields when creating leads. This issue has been patched in version 3.0.13.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improperly Controlled Modification of Dynamically-Determined Object Attributes
The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.
How developers prevent this class of flaw
- If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists. For applications written with Ruby on Rails, use the attr_accessible (allowlist) or attr_protected (denylist) macros in each class that may be used in mass assignment.
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/FlowiseAI/Flowise/security/advisories/GHSA-mq4r-h2gh-qv7xExploit, Mitigation
Patches and release notes
- github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.13Product, Release Notes
Other vulnerabilities in Flowise
- 8.5 High severity
- 8.5 High severity
- 7.5 High severity
- 8.3 High severity
- 7.7 High severity
- 7.7 High severity
Recent Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerabilities
- 8.8 High severity
- 8.2 High severity
- 7.6 High severity
- 7.5 High severity
- 10.0 Critical severity
- 8.1 High severity
Spotted an error? Tell us.