Flowise Cors Misconfiguration in packages/server/src/index.ts

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-36421: 8.49% estimated exploitation activity in the next 30 days; percentile 95.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Flowise is a drag & drop user interface to build a customized large language model flow. In version 1.4.3 of Flowise, A CORS misconfiguration sets the Access-Control-Allow-Origin header to all, allowing arbitrary origins to connect to the website. In the default configuration (unauthenticated), arbitrary origins may be able to make requests to Flowise, stealing information from the user. This CORS misconfiguration may be chained with the path injection to allow an attacker attackers without access to Flowise to read arbitrary files from the Flowise server. As of time of publication, no known patches are available.

Published by the source

5 Aug 2024, 21:29 UTC

Last modified by the source

5 Aug 2024, 22:11 UTC

Source last checked

26 Oct 2026, 12:31 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-66f2-xxgm-f6xp

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-66f2-xxgm-f6xp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-36421

Advisory: Flowise Cors Misconfiguration in packages/server/src/index.ts
IDs: CVE-2024-36421, GHSA-66f2-xxgm-f6xp
Record: https://patchnext.com/advisories/cve-2024-36421 (revision 3, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm flowise: affected <= 1.4.3

## Suggested inspection (read-only)
- `npm ls flowise --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on flowise.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-66f2-xxgm-f6xp (OSV record GHSA-66f2-xxgm-f6xp lists affected ranges: npm flowise >=0 <=1.4.3)
- Verified: https://github.com/advisories/GHSA-66f2-xxgm-f6xp (GitHub-reviewed advisory GHSA-66f2-xxgm-f6xp lists affected ranges: npm flowise >=0 <=1.4.3)

Commands are suggestions: review each one before running it.