Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-56271Published 2026-07-12

CVE-2026-56271 — Flowise

critical

As of 2026-07-13, CVE-2026-56271 is a CRITICAL-severity vulnerability in Flowise, CVSS v3.1 9.8, EPSS 0.6% (49.3th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-56271, most recently “Chinese-Speaking 'Kapibala' Actor (Red Heron-Linked) Chains WordPress wp2shell, Zyxel GS1900, and Ubiquiti UniFi OS Flaws to Steal Government Data”.

CVSS v3.1
9.8/10Critical
EPSS
0.6%Higher than 49.3% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
6.9/10Threadlinqs triage score
Published
Updated 2026-07-13
CVSS v3.1 9.8 (CRITICAL) · CVSS v4.0 9.3 · EPSS 0.6% (higher than 49.3% of all scored CVEs) · Priority 6.9/10 · Published 2026-07-12

Last updated:

What is CVE-2026-56271?

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.

The record classifies CVE-2026-56271 under weakness class CWE-321. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 85 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.8 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0 base score
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
EPSS (FIRST)
0.6% probability of exploitation in the next 30 days, higher than 49.3% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
6.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-12, last modified 2026-07-13

Is CVE-2026-56271 being exploited?

No public exploitation evidence for CVE-2026-56271 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-07-13. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.

Affected products and versions

  • Flowise: Flowise

How to fix CVE-2026-56271

Vendor advisory: https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-cc4f-hjpj-g9p8. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-56271

1 tracked threat in the Threadlinqs corpus references CVE-2026-56271, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Third-party advisory