Servers and applications
GHSA-cc4f-hjpj-g9p8
Weak Default JWT Secrets
- Severity
- Medium 5.6
- Published
- 15 Apr 2026
- Last changed
- 15 Apr 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.1.0
- Attack
- Needs local access · Only under certain conditions · Needs an administrator account · Needs someone to click or open something
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N- Sources
- Project advisories (GitHub)
Description
Detection Method: Kolega.dev Deep Code Scan
JWT secrets have weak hardcoded defaults ('auth_token', 'refresh_token', 'AUDIENCE', 'ISSUER'). Attackers can forge valid JWTs and impersonate any user.
All JWT defaults are weak strings. Refresh token falls back to auth token which is a design flaw. If any environment variable is unset, weak default is used.
Complete authentication bypass. Attackers can forge valid JWTs for any user account. No authentication required to access protected endpoints. Can escalate to admin access.
The JWT secrets have genuinely weak hardcoded defaults ('auth_token', 'refresh_token', 'AUDIENCE', 'ISSUER') at lines 29-34. If an administrator deploys without setting the environment variables JWT_AUTH_TOKEN_SECRET, JWT_REFRESH_TOKEN_SECRET, JWT_AUDIENCE, and JWT_ISSUER, the application will use these trivially guessable values.
Affected software
| Software | Affected versions |
|---|---|
FlowiseServers and applications · github:flowiseai/flowise |
|
About Flowise
Build AI Agents, Visually
- Archived
- Yes, no longer maintainedGitHub
- Weekly downloads (npm)
- 6,604npm, 15 Nov 2026
- Docker Hub pulls
- 7,390,661Docker Hub, 15 Nov 2026
- GitHub stars
- 55,573GitHub, 15 Nov 2026
- Forks
- 25,094GitHub, 15 Nov 2026
- Latest release
- [email protected]GitHub, 15 Nov 2026
- Released
- 29 Jul 2026GitHub
- First published on GitHub
- 31 Mar 2023GitHub
Source code Website Docker image Package
Vulnerabilities in Flowise
- In our list
- 171
- Published in the last 12 months
- 149
- Critical, last 12 months
- 41
- High, last 12 months
- 70
- Known exploited
- 0
- CVE-2026-130796Flowise 3.1.3 through 3.1.4 MCP Server Token Disclosure via Public Chatflow EndpointHigh 8.8 17 Nov 2026
- CVE-2026-130615Flowise through 3.1.4 SSRF via DNS Rebinding in Playwright and Puppeteer LoadersHigh 7.6 17 Nov 2026
- CVE-2026-127214Flowise 3.1.4 SSRF Bypass via Custom Function SandboxMedium 6.3 13 Nov 2026
- CVE-2026-119978Flowise through 3.1.4 Custom Function Sandbox Escape RCE via LocalFileStoreCritical 9.0 30 Oct 2026
- CVE-2026-90580A vulnerability was found in FlowiseAI Flowise up to 3.0.2. This vulnerability affects the function axios.post of the file packages/server/src/controllers/evaluations/index.ts of the component Evaluations Endpoint. The manipulation of the argument Host/X-Forwarded-Proto results in server-side request forgery. The attack may be launched remotely. The exploit has been made public and could be…Low 2.1 13 Sept 2026
- CVE-2026-90535Flowise versions before 3.1.4 contain an unauthenticated denial of service vulnerability in the /api/v1/text-to-speech/abort endpoint that accepts user-supplied chatflowId and chatId without ownership verification. Attackers can terminate active chatflow predictions for any user by submitting requests with known chatflow and chat identifiers, causing targeted service disruption.Medium 6.3 12 Sept 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-cc4f-hjpj-g9p8
- github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-cc4f-hjpj-g9p8