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.
CVE-2026-70636
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. the CNA's CVSS baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
August 6, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 6, 2026cve-advisories/2026/Flowise/CVE-2026-70636.md at main · Caycon/cve-advisories · GitHub
https://github.com/Caycon/cve-advisories/blob/main/2026/Flowise/CVE-2026-70636.mdVendor Advisories for CVE-2026-70636(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 31× in last 7d / 63× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 08:42 UTCGHSA enrichment
- 2026-08-19 20:28 UTCEG score recompute
- 2026-08-19 20:28 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 08:13 UTCGHSA enrichment
- 2026-08-18 19:59 UTCEG score recompute
- 2026-08-18 19:59 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 07:45 UTCGHSA enrichment
- 2026-08-17 19:24 UTCEG score recompute
- 2026-08-17 19:24 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:33 UTCGHSA enrichment
- 2026-08-16 18:08 UTCEG score recompute
- 2026-08-16 18:08 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:53 UTCEG score recompute
- 2026-08-16 05:53 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 17:39 UTCGHSA enrichment
- 2026-08-15 05:25 UTCEG score recompute
- 2026-08-15 05:25 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
Show 38 moreShow fewer
- 2026-08-14 17:10 UTCEG score recompute
- 2026-08-14 17:10 UTCGHSA enrichment
- 2026-08-14 06:17 UTCEG score recompute
- 2026-08-14 06:17 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 18:03 UTCGHSA enrichment
- 2026-08-13 05:49 UTCGHSA enrichment
- 2026-08-12 17:34 UTCEG score recompute
- 2026-08-12 17:34 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 05:20 UTCGHSA enrichment
- 2026-08-11 17:05 UTCEG score recompute
- 2026-08-11 17:05 UTCGHSA enrichment
- 2026-08-11 04:50 UTCEG score recompute
- 2026-08-11 04:50 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 16:36 UTCGHSA enrichment
- 2026-08-10 04:18 UTCGHSA enrichment
- 2026-08-09 16:04 UTCEG score recompute
- 2026-08-09 16:04 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 03:50 UTCEG score recompute
- 2026-08-09 03:50 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 15:36 UTCGHSA enrichment
- 2026-08-08 03:22 UTCEG score recompute
- 2026-08-08 03:22 UTCGHSA enrichment
- 2026-08-08 02:52 UTCEG score recompute
- 2026-08-08 02:52 UTCGHSA enrichment
- 2026-08-07 18:27 UTCEG score recompute
- 2026-08-07 18:27 UTCGHSA enrichment
- 2026-08-07 17:27 UTCEG score recompute
- 2026-08-07 17:27 UTCGHSA enrichment
- 2026-08-07 10:52 UTCEG score recompute
- 2026-08-07 10:52 UTCGHSA enrichment
- 2026-08-06 22:38 UTCEG score recompute
- 2026-08-06 22:15 UTCEG score recompute
- 2026-08-06 22:15 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-70636?
When was CVE-2026-70636 disclosed?
Is CVE-2026-70636 actively exploited?
What is the CVSS score of CVE-2026-70636?
How do I remediate CVE-2026-70636?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-70636
Is Your Infrastructure Affected by CVE-2026-70636?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.