How severe is CVE-2026-70636?

CVE-2026-70636 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2026-70636 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-70636?

CVE-2026-70636 affects Flowiseai Flowise. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-70636?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-70636 published?

CVE-2026-70636 was published on 2026-08-06 and last updated on 2026-09-15.

CVE-2026-70636

CVE-2026-70636 is a high-severity vulnerability in Flowiseai Flowise with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-862.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v4: 8.7
EPSS exploit prediction: 1% (50th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-862
Affected product: Flowiseai Flowise
Published: 2026-08-06
Last modified: 2026-09-15

Description

Flowise through 3.1.4 contains an authentication bypass vulnerability that allows unauthenticated attackers to access the OAuth2 credential refresh endpoint by exploiting prefix-based whitelist matching in the authentication middleware defined in packages/server/src/utils/constants.ts. Attackers can send a POST request to the oauth2-credential refresh route with a trailing credential identifier to bypass all authentication and authorization checks, triggering unauthorized OAuth token rotation against credentials belonging to any workspace and potentially disrupting dependent OAuth integrations. This is a bypass of CVE-2026-41273.

Frequently asked questions

What is CVE-2026-70636?: Flowise through 3.1.4 contains an authentication bypass vulnerability that allows unauthenticated attackers to access the OAuth2 credential refresh endpoint by exploiting prefix-based whitelist matching in the authentication middleware defined in packages/server/src/utils/constants.ts. Attackers can send a POST request to the oauth2-credential refresh route with a trailing credential identifier to bypass all authentication and authorization checks, triggering unauthorized OAuth token rotation against credentials belonging to any workspace and potentially disrupting dependent OAuth integrations. This is a bypass of CVE-2026-41273.
How severe is CVE-2026-70636?: CVE-2026-70636 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2026-70636 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-70636?: CVE-2026-70636 affects Flowiseai Flowise. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-70636?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-70636 published?: CVE-2026-70636 was published on 2026-08-06 and last updated on 2026-09-15.

References

Affected products (1)

cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*

More vulnerabilities in Flowiseai Flowise

CVE-2026-70478 — Critical (CVSS 10.0): Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the POST…
CVE-2025-71338 — Critical (CVSS 10.0): Flowise through 2.2.7 fails to sanitize path segments in the document-store loader endpoint, allowing unauthenticated…
CVE-2025-59528 — Critical (CVSS 10.0): Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5, Flowise is…
CVE-2026-73602 — Critical (CVSS 9.9): Flowise before 3.1.3 contains a sandbox escape vulnerability in the vm2 JavaScript sandbox that allows authenticated…
CVE-2026-67622 — Critical (CVSS 9.9): Flowise through 3.1.4 contains an insecure direct object reference vulnerability in the OpenAI Assistants integration…
CVE-2026-56274 — Critical (CVSS 9.9): Flowise before 3.1.2 contains multiple OS command injection vulnerabilities in the Custom MCP Server feature due to…

All CVEs affecting Flowiseai Flowise →

Other CWE-862 (Missing Authorization) vulnerabilities

CVE-2026-101000 — Critical (CVSS 10.0): A vulnerability was determined in Netcore NBR100V2 1.3.240614.030928. This affects the function uci.apply of the file…
CVE-2026-97360 — Critical (CVSS 10.0): HFS2 version 2.4.0 and earlier contains an unauthenticated arbitrary file access vulnerability that allows…
CVE-2026-65381 — Critical (CVSS 10.0): A validation issue existed in the entitlement verification. This issue was addressed with improved validation of the…
CVE-2026-81648 — Critical (CVSS 10.0): The CryptoPayment Gateway WordPress plugin from 1.2.1 to 1.2.2 does not apply an authorization check on one of its AJAX…
CVE-2026-77770 — Critical (CVSS 10.0): The miniOrange 2FA WordPress plugin before 6.3.1, miniOrange 2FA WordPress plugin before 19.3 does not require a…
CVE-2026-65667 — Critical (CVSS 10.0): Missing authorization in Microsoft Teams allows an unauthorized attacker to elevate privileges over a network.

Browse all CWE-862 (Missing Authorization) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE:

18.228.228.159 (ipv4-addr)
3.19.213.118 (ipv4-addr)