Weak Hardcoded JWT Secrets in Flowise Authentication
Flowise
Flowise uses weak hardcoded default JWT secrets and parameters in its enterprise passport authentication middleware when environment variables are unset. Attackers can forge valid JWT tokens to impersonate any user on the platform.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 9.8
- EPSS
- 0.01 · top 49% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 12 Jul 2026
- last update
- 12 Jul 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-07-12CVE-2026-56271: Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses weak hardcoded default JWT secrets ('auth_token',…NVD · nvd.nist.gov/vuln/detail/CVE-2026-56271
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- tags
- weak-cryptojwt
- dates
- happened 12 Jul 2026 · first reported 12 Jul 2026
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 10:04Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# Weak Hardcoded JWT Secrets in Flowise Authentication
https://gcdradar.vercel.app/incidents/weak-hardcoded-jwt-secrets-in-flowise-authentication · AIR-2026-1159 · closed 2026-07-12
- Lane: Patch now
- Severity: 2 (Disclosed vulnerability)
- Fix status: Fix status unknown
- First reported: 2026-07-12
- AI role: Attack on AI
- Products: Flowise
- CVE ids: CVE-2026-56271
- CVSS: 9.8
## Summary
Flowise uses weak hardcoded default JWT secrets and parameters in its enterprise passport authentication middleware when environment variables are unset. Attackers can forge valid JWT tokens to impersonate any user on the platform.
## What to do
No action recorded; read the sources below and the vendor's advisory.
## Latest updates
- 2026-07-12: CVE-2026-56271: Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses weak hardcoded default JWT secrets ('auth_token',… (https://nvd.nist.gov/vuln/detail/CVE-2026-56271)
## Sources
- 2026-07-12 NVD: CVE-2026-56271: Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses weak hardcoded default JWT secrets ('auth_token',… https://nvd.nist.gov/vuln/detail/CVE-2026-56271
Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.Related
- closed8.7Flowise CVE-2026-71962: Flowise Missing Authorization on Assistant File Download
Patch now · Disclosed · since 10 Aug 2026 · CVE-2026-71962
AI - closed7.7Flowise CVE-2026-67620: Flowise SSRF Vulnerability in Metadata Guard
Patch now · Disclosed · since 8 Aug 2026 · CVE-2026-67620
AI - closed7.6Flowise CVE-2026-67621: Flowise missing authorization in document store routes
Patch now · Disclosed · since 6 Aug 2026 · CVE-2026-67621
AI - closed9.9Flowise CVE-2026-67622: Flowise IDOR vulnerability in OpenAI Assistants integration
Patch now · Disclosed · since 6 Aug 2026 · CVE-2026-67622
AI - closed8.7Flowise CVE-2026-70636: Flowise auth bypass vulnerability in OAuth2 endpoint
Patch now · Disclosed · since 6 Aug 2026 · CVE-2026-70636
AI - closedFlowise Flowise Unauthenticated TTS Credential Abuse
Patch now · Disclosed · since 4 Aug 2026
AI