CVE-2026-69258
Unauthenticated config-injection in Flowise lets attackers control flow execution context.
Is CVE-2026-69258 being exploited?
Not confirmed. CVE-2026-69258 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-69258?
CVE-2026-69258 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-69258?
Yes. A fix has been recorded for CVE-2026-69258. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-69258 affect?
CVE-2026-69258 affects Flowise < 3.1.3, POST /api/v1/prediction/:id endpoint, packages/server/src/utils/buildChatflow.ts, packages/server/src/utils/index.ts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69258?
Upgrade to Flowise 3.1.3; restrict or require auth on prediction API
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can inject/overwrite flow context (chatId, sessionId, chatHistory) and control $flow.* vars, enabling prompt injection, impersonation, and data exfiltration.
Patch when possible
- affected< 3.1.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.