{"answers":{"affected":"4 open source packages ship an affected version, including n8n. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-72772 in the wild and no public exploit code.","fix":"Upgrade n8n to a fixed version for your release line: 2.31.5 or 2.32.1.","what":"CVE-2026-72772 is a high-severity authentication bypass vulnerability in N8n N8n, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72772 and fix it if it is affected.\n\nWhat it is: CVE-2026-72772 is a high-severity authentication bypass vulnerability in N8n N8n, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72772 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- n8n (npm): affected all versions; fixed in 2.31.5\n- n8n (npm): affected all versions; fixed in 2.31.5\n- n8n (npm): affected from 2.32.0; fixed in 2.32.1\n- n8n (npm): affected from 2.32.0; fixed in 2.32.1\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-72772/ (Markdown: https://insights.sbomify.com/CVE-2026-72772/index.md)","id":"CVE-2026-72772","markdown":"https://insights.sbomify.com/CVE-2026-72772/index.md","name":"CVE-2026-72772","record":{"aliases":["GHSA-8342-988q-86cr","GHSA-cwxf-925x-2ccm","MINI-9xfx-xh8f-q24h","MINI-g7q9-hv22-4ggw","ROOT-APP-NPM-GHSA-8342-988q-86cr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"n8n workflow automation","requires_auth":"low_privilege","summary":"Attackers can take over any user account via Token Exchange Embed Login if the feature is enabled and trusted keys are configured, due to missing email verification checks.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"n8n","vendor":"n8n"}],"cvss":{"score":8.9,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-640","name":"Weak Password Recovery Mechanism for Forgotten Password"}],"description":"n8n before 2.32.1 (and before 2.31.5) is vulnerable to account takeover via the Token Exchange Embed Login feature. When a validly-signed incoming token was matched to a local account by its email claim, the service did not verify that the email claim was verified, nor that the trusted key's permitted role ceiling covered that account. As a result, anyone able to obtain a token accepted by a configured trusted key (for example, a trusted issuer emitting unverified email addresses) could authenticate as any existing user and gain full account control. This issue only affects instances where the embed login feature is enabled and at least one trusted key source is configured.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"n8n before 2.32.1 Authentication Bypass via Token Exchange","id":"CVE-2026-72772","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"n8n:n8n","products":["n8n:n8n"],"type":"auth_bypass","year":"2026"},"n_packages":4,"n_references":2,"next":{"headline":"n8n before 2.32.1 Path Traversal via computer-use search_files","id":"CVE-2026-72773"},"packages":[{"ecosystem":"npm","fixed":["2.31.5"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":null,"source":"GHSA-8342-988q-86cr"},{"ecosystem":"npm","fixed":["2.31.5"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":"pkg:npm/n8n","source":"GHSA-8342-988q-86cr"},{"ecosystem":"npm","fixed":["2.32.1"],"introduced":["2.32.0"],"last_affected":[],"package":"n8n","purl":null,"source":"GHSA-8342-988q-86cr"},{"ecosystem":"npm","fixed":["2.32.1"],"introduced":["2.32.0"],"last_affected":[],"package":"n8n","purl":"pkg:npm/n8n","source":"GHSA-8342-988q-86cr"}],"prev":{"headline":"n8n before 2.32.1 Credential Restriction Bypass via AI/LLM Nodes","id":"CVE-2026-72771"},"products":["n8n"],"published":"2026-08-11","related":[{"cvss_score":10,"headline":"n8n Improper Control of Dynamically-Managed Code Resources","id":"CVE-2025-68613","kev_date_added":"2026-03-11","published":"2025-12-19"},{"cvss_score":10,"headline":"n8n is vulnerable to Remote Code Execution via Arbitrary File Write","id":"CVE-2026-21877","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":10,"headline":"n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling","id":"CVE-2026-21858","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":9.9,"headline":"n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution","id":"CVE-2026-1470","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":9.9,"headline":"n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node","id":"CVE-2025-68668","kev_date_added":null,"published":"2025-12-26"},{"cvss_score":9.5,"headline":"n8n has Unauthenticated Expression Evaluation via Form Node","id":"CVE-2026-27493","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":9.4,"headline":"n8n: HTTP Request Node Pagination Prototype Pollution to RCE","id":"CVE-2026-44789","kev_date_added":null,"published":"2026-06-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["n8n-io"]},"summary":"Attackers can take over any user account via Token Exchange Embed Login if the feature is enabled and trusted keys are configured, due to missing email verification checks.","url":"https://insights.sbomify.com/CVE-2026-72772/"}