{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-77069 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-77069 is a low-severity server-side request forgery vulnerability in N8n N8n, published on 20 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-77069 and fix it if it is affected.\n\nWhat it is: CVE-2026-77069 is a low-severity server-side request forgery vulnerability in N8n N8n, published on 20 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-77069 in the wild and no public exploit code.\n\nAffected product: N8n N8n. 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-77069/ (Markdown: https://insights.sbomify.com/CVE-2026-77069/index.md)","id":"CVE-2026-77069","markdown":"https://insights.sbomify.com/CVE-2026-77069/index.md","name":"CVE-2026-77069","record":{"aliases":["GHSA-4x7w-pwq5-598q","GHSA-c4f6-59xq-95ww","MINI-9r5q-5fwq-h2gq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"n8n workflow automation","requires_auth":"low_privilege","summary":"An attacker with credential-creation permissions can bypass SSRF protections in n8n's OAuth2 token exchange to access internal network resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"n8n","vendor":"n8n"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"n8n before 1.123.69, 2.33.4, and 2.34.1 contains an SSRF protection bypass in the OAuth2 credential authorization-code-to-access-token exchange. While OAuth2 discovery and dynamic-client-registration requests use n8n's SSRF-protected HTTP client, the token exchange uses a separate client with no SSRF guard. A user with credential-creation permissions can set the access-token URL to an internal address and complete the OAuth2 flow, causing n8n to send a fixed-shape token-exchange POST to that target and reflect its response body back to the attacker (limited to what the target returns to this specific request).","ecosystems":[],"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 1.123.69 SSRF Protection Bypass via OAuth2","id":"CVE-2026-77069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"n8n:n8n","products":["n8n:n8n"],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"n8n before 1.123.69 NoSQL Injection via MongoDB Node","id":"CVE-2026-77070"},"packages":[],"prev":{"headline":"n8n before 2.34.1 Remote Code Execution via Path Traversal","id":"CVE-2026-77068"},"products":["n8n"],"published":"2026-08-20","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":"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":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["n8n-io"]},"summary":"An attacker with credential-creation permissions can bypass SSRF protections in n8n's OAuth2 token exchange to access internal network resources.","url":"https://insights.sbomify.com/CVE-2026-77069/"}