{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100606 exists.","fix":"No fix has been published for CVE-2026-100606 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100606 is a critical authentication bypass vulnerability in FlowiseAI Flowise, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-100606 and fix it if it is affected.\n\nWhat it is: CVE-2026-100606 is a critical authentication bypass vulnerability in FlowiseAI Flowise, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100606 exists.\n\nAffected product: FlowiseAI Flowise. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100606/ (Markdown: https://insights.sbomify.com/CVE-2026-100606/index.md)","id":"CVE-2026-100606","markdown":"https://insights.sbomify.com/CVE-2026-100606/index.md","name":"CVE-2026-100606","record":{"aliases":["GHSA-mgrx-3hqw-485h","GHSA-vf3j-89vf-r697"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Flowise AI platform","requires_auth":"none","summary":"Attackers can hijack pending user invitations in Flowise Enterprise by exploiting an SSO logic flaw, gaining unauthorized access to organizations without valid tokens.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callback arrives with an email matching a user whose status is INVITED, verifyAndLogin (SSOBase.ts:80-94) copies the user record from the database — including the server-stored single-use invitation tempToken — into the data passed to AccountService.register(). The register handler's token lookup, email match, and expiry checks therefore pass trivially against the server's own token instead of a caller-supplied one, and the account and its organization membership are flipped to ACTIVE. As a result, anyone able to authenticate at any configured SSO provider using a pending invitee's email address as the email claim can take over that invitation and obtain the invited user's access to the organization without ever possessing the emailed invitation token, for as long as the invitation is valid (24 hours by default). At the time of the advisory no patched version was available.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Flowise through 3.1.4 Authentication Bypass via SSO Email Match","id":"CVE-2026-100606","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Flowise through 3.1.4 Authentication Bypass via Email-Only SSO","id":"CVE-2026-100607"},"packages":[],"prev":{"headline":"Flowise through 3.1.4 Missing Authorization via Chat Message Routes","id":"CVE-2026-100605"},"products":["Flowise"],"published":"2026-09-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["FlowiseAI"]},"summary":"Attackers can hijack pending user invitations in Flowise Enterprise by exploiting an SSO logic flaw, gaining unauthorized access to organizations without valid tokens.","url":"https://insights.sbomify.com/CVE-2026-100606/"}