Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the unauthenticated POST /api/v1/prediction/:id endpoint accepted an overrideConfig object and unconditionally spread it into internal flowConfig and flowData objects in packages/server/src/utils/buildChatflow.ts and packages/server/src/utils/index.ts without checking apiOverrideStatus. This allowed unauthenticated attackers to inject arbitrary properties into the flow execution context of any public chatflow, overwrite values such as chatId, sessionId, and chatHistory, and control values resolved through $flow.* template variables consumed by flow nodes. This issue is fixed in version 3.1.3.
CVE-2026-69258
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. 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).
- 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
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 71(Attend)EG Risk 71/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 computedSeverity88% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
August 4, 2026
Last Modified
August 5, 2026
Advisory Details (4)
Auto-updated Aug 4, 2026Unauthenticated Property Injection into Flow Execution Context via Ungated `overrideConfig` Spread in Prediction API · Advisory · FlowiseAI/Flowise · GitHub
https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-6vh2-wg4h-4vwj[email protected]
Patch available: FlowiseAI/Flowise [email protected]
https://github.com/FlowiseAI/Flowise/releases/tag/[email protected]bugfix:308 | remove ungated overrideConfig spread
Patch available: FlowiseAI/Flowise [email protected] (PR #6279 merged 2026-05-07)
https://github.com/FlowiseAI/Flowise/pull/6279commit 23b997ee5ef9 (FlowiseAI/Flowise)
Patch available: FlowiseAI/Flowise [email protected] (contains commit 23b997ee5ef9)
https://github.com/FlowiseAI/Flowise/commit/23b997ee5ef9e269b628bad0f56f1ecb86bd2fcaVendor Advisories for CVE-2026-69258(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| flowise | — | 3.1.3 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 37× 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 22:56 UTCEPSS rescore
- 2026-08-19 22:46 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 23:10 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 23:34 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 23:57 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:08 UTCEG score recompute
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 12:33 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 01:08 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:32 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 14:08 UTCEG score recompute
- 2026-08-11 02:20 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 14:55 UTCEG score recompute
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 03:08 UTCEG score recompute
Show 12 moreShow fewer
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 03:32 UTCEG score recompute
- 2026-08-06 16:08 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 04:20 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 16:32 UTCEG score recompute
- 2026-08-05 15:29 UTCEG score recompute
- 2026-08-04 17:23 UTCEG score recompute▲ 8.80
- 2026-08-04 17:23 UTCNVD updateCVSS v3 → 8.8 · CVSS v4 → 8.8
- 2026-08-04 16:07 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-69258?
When was CVE-2026-69258 disclosed?
Is CVE-2026-69258 actively exploited?
What is the CVSS score of CVE-2026-69258?
How do I remediate CVE-2026-69258?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69258
Is Your Infrastructure Affected by CVE-2026-69258?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.