CVE-2026-70474

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise has three OAuth2 credential endpoints that look up credentials by id alone with no workspaceId filter. The authorize, callback, and refresh handlers query the Credential table by id only; callback and refresh are whitelisted from authentication. This allows any authenticated user to initiate OAuth2 flows against credentials belonging to other workspaces, allows an unauthenticated attacker to forge OAuth2 callbacks to overwrite tokens in any credential, and allows an unauthenticated attacker to refresh tokens for any credential. The affected routes include /api/v1/oauth2-credential/authorize/, /api/v1/oauth2-credential/callback?code=ATTACKER_AUTH_CODE&state=, and /api/v1/oauth2-credential/refresh/. This issue is fixed in version 3.1.3.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100CISA SSVC

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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 4, 2026

Last Modified

September 11, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

Cross-Workspace OAuth2 Credential Metadata Leak · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-wch5-xp77-fxg4
github_release Patch Available

[email protected]

Patch available: FlowiseAI/Flowise [email protected]

https://github.com/FlowiseAI/Flowise/releases/tag/[email protected]

Vendor Advisories for CVE-2026-70474(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
flowise—
  • every version up to 3.1.3: fixed in 3.1.3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 50× 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.

Showing the most recent 100 of 111 total refreshes for this CVE.

  1. 2026-10-04 23:39 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-04 06:10 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 01:55 UTCEG score recompute
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 10:07 UTCEG score recompute
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 02:26 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 06:25 UTCEG score recompute
  12. 2026-09-28 13:52 UTCEPSS rescore
  13. 2026-09-27 18:00 UTCEG score recompute
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-25 04:40 UTCEG score recompute
  17. 2026-09-24 04:26 UTCEG score recompute
  18. 2026-09-23 17:54 UTCEPSS rescore
  19. 2026-09-23 03:45 UTCEG score recompute
  20. 2026-09-22 03:18 UTCEG score recompute
  21. 2026-09-21 21:09 UTCEPSS rescore
  22. 2026-09-20 20:52 UTCEG score recompute
  23. 2026-09-20 20:16 UTCEPSS rescore
  24. 2026-09-19 23:22 UTCEG score recompute
  25. 2026-09-19 07:57 UTCEG score recompute
Show 75 more
  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 04:25 UTCEG score recompute
  3. 2026-09-17 01:11 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEG score recompute
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 16:47 UTCEG score recompute
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-13 22:06 UTCEG score recompute
  10. 2026-09-12 21:41 UTCEG score recompute
  11. 2026-09-12 15:02 UTCEPSS rescore
  12. 2026-09-11 21:16 UTCEG score recompute▲ 0.50
  13. 2026-09-11 21:16 UTCNVD updateCVSS v3 → 8.1
  14. 2026-09-11 15:20 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 14:53 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 09:15 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 18:31 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 18:57 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 18:32 UTCEG score recompute
  25. 2026-09-05 15:31 UTCEPSS rescore
  26. 2026-09-05 04:06 UTCEG score recompute
  27. 2026-09-04 10:07 UTCEG score recompute
  28. 2026-09-04 05:07 UTCEPSS rescore
  29. 2026-09-03 07:27 UTCEG score recompute
  30. 2026-09-02 14:12 UTCEPSS rescore
  31. 2026-09-01 20:49 UTCEG score recompute
  32. 2026-09-01 13:54 UTCEPSS rescore
  33. 2026-09-01 04:40 UTCEPSS rescore
  34. 2026-08-30 22:11 UTCEG score recompute
  35. 2026-08-30 19:17 UTCEPSS rescore
  36. 2026-08-30 09:59 UTCEG score recompute
  37. 2026-08-30 01:22 UTCEPSS rescore
  38. 2026-08-29 21:46 UTCEG score recompute
  39. 2026-08-28 21:42 UTCEPSS rescore
  40. 2026-08-28 01:23 UTCEG score recompute
  41. 2026-08-27 00:58 UTCEG score recompute
  42. 2026-08-26 14:47 UTCEPSS rescore
  43. 2026-08-26 00:32 UTCEG score recompute
  44. 2026-08-25 13:49 UTCEPSS rescore
  45. 2026-08-24 23:36 UTCEG score recompute
  46. 2026-08-24 11:22 UTCEG score recompute
  47. 2026-08-23 10:56 UTCEG score recompute
  48. 2026-08-23 00:19 UTCEPSS rescore
  49. 2026-08-22 10:31 UTCEG score recompute
  50. 2026-08-21 23:49 UTCEPSS rescore
  51. 2026-08-21 10:05 UTCEG score recompute
  52. 2026-08-20 22:56 UTCEPSS rescore
  53. 2026-08-19 21:27 UTCEG score recompute
  54. 2026-08-19 17:04 UTCEPSS rescore
  55. 2026-08-18 20:56 UTCEG score recompute
  56. 2026-08-18 13:49 UTCEPSS rescore
  57. 2026-08-18 13:49 UTCEPSS rescore
  58. 2026-08-17 20:32 UTCEG score recompute
  59. 2026-08-17 13:47 UTCEPSS rescore
  60. 2026-08-16 20:06 UTCEG score recompute
  61. 2026-08-16 14:56 UTCEPSS rescore
  62. 2026-08-16 14:56 UTCEPSS rescore
  63. 2026-08-16 07:53 UTCEG score recompute
  64. 2026-08-16 02:15 UTCEPSS rescore
  65. 2026-08-15 07:28 UTCEG score recompute
  66. 2026-08-15 01:31 UTCEPSS rescore
  67. 2026-08-14 07:02 UTCEG score recompute
  68. 2026-08-13 22:00 UTCEPSS rescore
  69. 2026-08-12 18:25 UTCEG score recompute
  70. 2026-08-12 13:51 UTCEPSS rescore
  71. 2026-08-11 17:58 UTCEG score recompute
  72. 2026-08-11 05:45 UTCEG score recompute
  73. 2026-08-11 00:00 UTCEPSS rescore
  74. 2026-08-09 17:08 UTCEG score recompute
  75. 2026-08-09 13:47 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-70474?
CVE-2026-70474 is a high vulnerability published on August 4, 2026. Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise has three OAuth2 credential endpoints that look up credentials by id alone with no workspaceId filter. The authorize, callback, and refresh handlers query the Credential table…
When was CVE-2026-70474 disclosed?
CVE-2026-70474 was first published on August 4, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70474 actively exploited?
CVE-2026-70474 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70474?
CVE-2026-70474 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-70474?
A fix for CVE-2026-70474 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70474 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70474

Explore →

Is Your Infrastructure Affected by CVE-2026-70474?

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

Book a Demo →Browse All CVEs