CVE-2026-56271

What it is

Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses weak hardcoded default JWT secrets ('auth_token', 'refresh_token') and default audience and issuer values ('AUDIENCE', 'ISSUER') in the enterprise passport authentication middleware (packages/server/src/enterprise/middleware/passport/index.ts). When the corresponding environment variables (JWT_AUTH_TOKEN_SECRET, JWT_REFRESH_TOKEN_SECRET, JWT_AUDIENCE, JWT_ISSUER) are not set, the application silently falls back to these publicly known defaults, allowing an attacker to forge valid JWTs and impersonate any user, including administrators, resulting in authentication bypass.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-12 12:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-25 15:10 UTC Last updatedMost recent change to the record

Details

Published

2026-07-12 12:16 UTC

Last modified

2026-10-25 15:10 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-321

Record status

Analyzed

Affected

• Flowiseai Flowise < 3.1.0

Attack profile CVSS 4.0 · 9.3

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

None

Confidentiality

High

Integrity

High

Availability

High