CVE-2026-69251
Authenticated RCE via TypeORM additionalConfig in Flowise <3.1.3
Is CVE-2026-69251 being exploited?
Not confirmed. CVE-2026-69251 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 1.7% probability of exploitation in the next 30 days.
How severe is CVE-2026-69251?
CVE-2026-69251 is rated Critical. 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-69251?
Yes. A fix has been recorded for CVE-2026-69251. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-69251 affect?
CVE-2026-69251 affects Flowise <3.1.3, RecordManager nodes (MySQL/Postgres/SQLite), AgentMemory nodes (MySQL/AgentMemory). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69251?
Upgrade to Flowise 3.1.3+, restrict uploads, and audit/rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can upload a JS payload and achieve remote code execution on the Flowise server via TypeORM entities, enabling full system compromise and data theft.
Immediate action required
- affected< 3.1.3
- 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.