CVE-2026-70636

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity75% × 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, 2026
No patch confirmed yet.
generic

The Future of Flowise

https://flowiseai.com/sunset
generic

cve-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.md

Vendor 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.

  1. 2026-08-20 08:42 UTCGHSA enrichment
  2. 2026-08-19 20:28 UTCEG score recompute
  3. 2026-08-19 20:28 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 08:13 UTCGHSA enrichment
  6. 2026-08-18 19:59 UTCEG score recompute
  7. 2026-08-18 19:59 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 07:45 UTCGHSA enrichment
  11. 2026-08-17 19:24 UTCEG score recompute
  12. 2026-08-17 19:24 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 06:33 UTCGHSA enrichment
  15. 2026-08-16 18:08 UTCEG score recompute
  16. 2026-08-16 18:08 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 05:53 UTCEG score recompute
  20. 2026-08-16 05:53 UTCGHSA enrichment
  21. 2026-08-16 02:15 UTCEPSS rescore
  22. 2026-08-15 17:39 UTCGHSA enrichment
  23. 2026-08-15 05:25 UTCEG score recompute
  24. 2026-08-15 05:25 UTCGHSA enrichment
  25. 2026-08-15 01:31 UTCEPSS rescore
Show 38 more
  1. 2026-08-14 17:10 UTCEG score recompute
  2. 2026-08-14 17:10 UTCGHSA enrichment
  3. 2026-08-14 06:17 UTCEG score recompute
  4. 2026-08-14 06:17 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 18:03 UTCGHSA enrichment
  7. 2026-08-13 05:49 UTCGHSA enrichment
  8. 2026-08-12 17:34 UTCEG score recompute
  9. 2026-08-12 17:34 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 05:20 UTCGHSA enrichment
  12. 2026-08-11 17:05 UTCEG score recompute
  13. 2026-08-11 17:05 UTCGHSA enrichment
  14. 2026-08-11 04:50 UTCEG score recompute
  15. 2026-08-11 04:50 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 16:36 UTCGHSA enrichment
  18. 2026-08-10 04:18 UTCGHSA enrichment
  19. 2026-08-09 16:04 UTCEG score recompute
  20. 2026-08-09 16:04 UTCGHSA enrichment
  21. 2026-08-09 13:47 UTCEPSS rescore
  22. 2026-08-09 03:50 UTCEG score recompute
  23. 2026-08-09 03:50 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 15:36 UTCGHSA enrichment
  26. 2026-08-08 03:22 UTCEG score recompute
  27. 2026-08-08 03:22 UTCGHSA enrichment
  28. 2026-08-08 02:52 UTCEG score recompute
  29. 2026-08-08 02:52 UTCGHSA enrichment
  30. 2026-08-07 18:27 UTCEG score recompute
  31. 2026-08-07 18:27 UTCGHSA enrichment
  32. 2026-08-07 17:27 UTCEG score recompute
  33. 2026-08-07 17:27 UTCGHSA enrichment
  34. 2026-08-07 10:52 UTCEG score recompute
  35. 2026-08-07 10:52 UTCGHSA enrichment
  36. 2026-08-06 22:38 UTCEG score recompute
  37. 2026-08-06 22:15 UTCEG score recompute
  38. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-70636?
CVE-2026-70636 is a high vulnerability published on August 6, 2026. 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…
When was CVE-2026-70636 disclosed?
CVE-2026-70636 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70636 actively exploited?
CVE-2026-70636 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.4% of all scored CVEs.
What is the CVSS score of CVE-2026-70636?
CVE-2026-70636 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-70636?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-70636, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-70636

Explore →

Is Your Infrastructure Affected by CVE-2026-70636?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.