Security readout for executives and security teams
Plain-English summary
Flowise through 3.1.4 may let one authenticated tenant access another tenant’s OpenAI Assistants resources because credential identifiers are trusted without verifying workspace ownership. This can expose sensitive metadata and listings and permit unauthorized file uploads across workspace boundaries, creating serious data-separation and integrity risk.
Executive priority
Treat this as an immediate priority for multi-workspace Flowise environments using OpenAI Assistants. Identify deployments and users, contain the integration if ownership checks cannot be confirmed, and obtain current vendor guidance. Investigate cross-workspace access before rotating potentially exposed credentials. No fixed version is named in the supplied sources.
Technical view
Missing workspace ownership validation in Assistants credential lookups creates a CWE-639 IDOR. Authenticated attackers can reference another workspace’s credential UUID, enumerate assistant metadata and file or vector-store listings, and upload files. The supplied CVSS score is 9.9, with high confidentiality and integrity impacts and low availability impact.
Likely exposure
Highest likely exposure is Flowise through 3.1.4 with multiple workspaces, authenticated untrusted users, and OpenAI Assistants configured. Authentication is required, but no user interaction or complex preconditions are described. The bundle does not establish whether single-workspace deployments or deployments without this integration are affected.
Exploitation context
The bundle marks KEV false and provides no evidence of active exploitation in the wild. A researcher disclosure contains exploit information, indicating technical reproducibility, but this does not establish real-world abuse. Attackers require authenticated network access and a credential UUID associated with another workspace.
Researcher notes
The defect is an authorization failure, not merely UUID exposure: every referenced credential must be bound to the requester’s workspace. The structured affected entry lists version “0,” while the narrative says through 3.1.4. Confirm exact affected and fixed versions with Flowise, and preserve relevant logs before remediation.
Mitigation direction
- Check Flowise vendor guidance immediately for a fixed or supported release; the supplied sources do not identify one.
- Restrict or disable the OpenAI Assistants integration until workspace-scoped authorization is confirmed.
- Limit Flowise access to trusted users and networks as an interim risk reduction.
- Rotate potentially exposed OpenAI-related credentials after investigating possible cross-workspace access.
Validation and detection
- Inventory Flowise deployments and confirm versions, workspace count, and OpenAI Assistants usage.
- Verify every Assistants credential lookup enforces ownership by the authenticated user’s workspace.
- Review available logs for cross-workspace credential, assistant, file, or vector-store references.
- Test authorization boundaries using controlled accounts and credentials in a non-production environment.
- Confirm vendor-recommended remediation prevents cross-workspace reads and unauthorized file uploads.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-67622 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L3.16VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.5HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Researcher DisclosureCVE reference, VulnCheck · technical-description, exploit
- Sunset AnnouncementCVE reference, VulnCheck · vendor-advisory
- https://www.vulncheck.com/advisories/flowise-idor-in-openai-assistants-integrationCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.