Flowise Pre-auth Arbitrary File Upload

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2025-71333: 0.90% estimated exploitation activity in the next 30 days; percentile 59.77 (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.

Summary An unauthorized attacker can leverage the whitelisted route /api/v1/attachments to upload arbitrary files when the storageType is set to local (default). Details When a new request arrives, the system first checks if the URL starts with /api/v1/. If it does, the system then verifies whether the URL is included in the whitelist (whitelistURLs). If the URL is whitelisted, the request proceeds; otherwise, the system enforces authentication. @ /packages/server/src/index.ts The whitelist is defined as follows This means that every route in the whitelist does not require authentication. Now, let's examine the /api/v1/attachments route. @ /packages/server/src/routes/attachments/index.ts After several calls, the request reaches the createFileAttachment function @ (packages/server/src/utils/createAttachment.ts) Initially, the function retrieves chatflowid and chatId from the request without any additional validation. The only check performed is whether these parameters exist in the…

Published by the source

13 Mar 2025, 22:38 UTC

Last modified by the source

8 Jul 2026, 07:35 UTC

Source last checked

26 Oct 2026, 12:36 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-h42x-xx2q-6v6g

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-h42x-xx2q-6v6g

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

# Patch Next advisory brief: CVE-2025-71333

Advisory: Flowise Pre-auth Arbitrary File Upload
IDs: CVE-2025-71333, GHSA-h42x-xx2q-6v6g
Record: https://patchnext.com/advisories/cve-2025-71333 (revision 3, source checked 26 Oct 2026, 12:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
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 <= 2.2.7

## 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-h42x-xx2q-6v6g (OSV record GHSA-h42x-xx2q-6v6g lists affected ranges: npm flowise >=0 <=2.2.7)
- Verified: https://github.com/advisories/GHSA-h42x-xx2q-6v6g (GitHub-reviewed advisory GHSA-h42x-xx2q-6v6g lists affected ranges: npm flowise >=0 <=2.2.7)

Commands are suggestions: review each one before running it.