CVE-2026-91938 Flowise before 3.1.4 Server-Side Request Forgery via document loaders
High 7.6
Published
Updated
Check this codebase for CVE-2026-91938 and fix it if it is affected.
What it is: CVE-2026-91938 is a high-severity vulnerability in FlowiseAI Flowise, published on 15 Sep 2026.
Exploitation: There is no known exploitation of CVE-2026-91938 in the wild and no public exploit code.
Affected product: FlowiseAI Flowise. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-91938/ (Markdown: https://insights.sbomify.com/CVE-2026-91938/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-91938?
CVE-2026-91938 is a high-severity vulnerability in FlowiseAI Flowise, published on 15 Sep 2026.
Official description
Flowise versions before 3.1.4 contain a server-side request forgery vulnerability in Cheerio, Playwright, and Puppeteer document loader nodes that bypass SSRF protection. Attackers can provide arbitrary URLs to fetch cloud metadata, internal services, and private network resources with response content returned as document text.
Weakness: CWE-918
Which versions are affected by CVE-2026-91938?
How do I fix CVE-2026-91938?
No fix has been published for CVE-2026-91938 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-91938 being exploited?
There is no known exploitation of CVE-2026-91938 in the wild and no public exploit code.
Sources
Also known as GHSA-9cvr-5wv9-2gxr, GHSA-j6jh-78h2-2667.