Security readout for executives and security teams
Plain-English summary
A Flowise endpoint could give unauthenticated attackers access tokens for connected services when they know a credential ID. Stolen tokens may expose external data or permit actions under the victim’s permissions. Attackers may also exhaust refresh-token quotas. Flowise 3.1.3 fixes the issue.
Executive priority
Treat as an immediate upgrade priority for exposed or externally reachable Flowise systems. Potential impact extends beyond Flowise into connected services, where stolen tokens could expose sensitive information or enable unauthorized actions. Prioritize instances holding high-privilege OAuth credentials.
Technical view
The whitelisted POST OAuth2 refresh endpoint requires no authentication. It decrypts the selected stored credential, submits its client secret and refresh token to the OAuth provider, then returns the refreshed access token. Exploitation is network-based, low complexity, and requires a credential ID but no user interaction.
Likely exposure
Exposure is highest for reachable Flowise deployments predating 3.1.3 that store OAuth2 credentials for connected services. An attacker must obtain or guess a credential ID. The bundle inconsistently lists affected versions as “< 3.1.2” while stating the issue exists before 3.1.3; verify exact versions against the advisory.
Exploitation context
The bundle reports no CISA KEV listing and provides no evidence of active exploitation. Nevertheless, the unauthenticated, network-accessible design and potential access to connected services make prompt remediation appropriate. Credential-ID discovery remains a prerequisite according to the supplied description.
Researcher notes
CWE-200 and CVSS 4.0 score 9.2 align with unauthenticated disclosure of OAuth access tokens. Scope includes confidentiality impact in Flowise and connected systems, with limited integrity impact. Evidence does not establish credential-ID predictability, public exploitation, or exploitation in the wild. The source bundle’s affected-version boundary is internally inconsistent.
Mitigation direction
- Upgrade Flowise to version 3.1.3 or later.
- Restrict network access to Flowise until upgrading is complete.
- Review connected services and revoke potentially exposed access or refresh tokens.
- Check the vendor advisory for any additional remediation guidance.
Validation and detection
- Confirm every Flowise deployment reports version 3.1.3 or later.
- Verify the refresh endpoint no longer responds successfully without authentication.
- Inventory OAuth2 credentials stored in affected Flowise instances.
- Review Flowise and provider logs for unexpected refresh activity or token use.
- Confirm connected-service tokens were revoked where exposure is suspected.
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-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-70478 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.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N
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
1 official scoreWe 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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N
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
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-qgvm-j2hm-6m38CVE reference, GitHub_M · x_refsource_CONFIRM
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.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.