Secuno
ENNL
Book demo

CVE-2026-91934

8.8 HIGH
  1. Published15 Sept 2026

Description

Flowise versions before 3.1.4 fail to validate file paths in the SQL Database Chain node when connecting to SQLite databases, allowing authenticated attackers to write arbitrary files. Attackers can write malicious SQLite databases to system directories or inject files into the web root to execute commands or perform stored XSS attacks.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-890409.8
Tencent Mass Service Engine in Cluster (MSEC) allows a remote, unauthenticated attacker…
CVE-2026-917718.8
Weights & Biases wandb before 0.29.0 fails to validate the file name from server…
CVE-2026-917518.3
Flextype CMS through 1.0.0-alpha.3 fails to properly validate id and new_id parameters…
CVE-2026-912008.8
DevSpace through 6.3.21 fails to reject parent-directory segments in tar entry names…
CVE-2026-500069.1
Anyquery is an SQL query engine built on top of SQLite. Prior to 0.4.5, anyquery server…
CVE-2026-163358.1
IBM DataStage on Cloud Pak for Data 5.4.0.0 IBM DataStage could allow a remote…

Frequently asked

Is CVE-2026-91934 being actively exploited?

CVE-2026-91934 is not in the CISA KEV catalog.

How severe is CVE-2026-91934?

CVE-2026-91934 has a CVSS 3.1 base score of 8.8, rated high.

How do I fix CVE-2026-91934?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-91934 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.