{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-118679 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-118679 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-118679 is a medium-severity vulnerability in n8n-io n8n, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-118679 and fix it if it is affected.\n\nWhat it is: CVE-2026-118679 is a medium-severity vulnerability in n8n-io n8n, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-118679 in the wild and no public exploit code.\n\nAffected product: n8n-io 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-118679/ (Markdown: https://insights.sbomify.com/CVE-2026-118679/index.md)","id":"CVE-2026-118679","markdown":"https://insights.sbomify.com/CVE-2026-118679/index.md","name":"CVE-2026-118679","record":{"aliases":["GHSA-3c3p-5959-3ghr","GHSA-r9rf-g62g-xq7v"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"n8n before 1.123.83, 2.41.4, and 2.42.1 contains a server-side request forgery vulnerability in the Slack Trigger webhook that allows unauthenticated attackers to exfiltrate Slack tokens by bypassing signature verification when no signing secret is set. Attackers who know the webhook URL can name a file to download, causing the node to send the workspace access token to an attacker host and return the response.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"n8n before 1.123.83, 2.41.4, and 2.42.1 Slack Token Exfiltration via Slack Trigger","id":"CVE-2026-118679","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"SiYuan 3.8.7 through 3.8.8 Path Traversal via GLOBALROOT Alias","id":"CVE-2026-118680"},"packages":[],"prev":{"headline":"n8n before 2.41.4 and 2.42.1 Prototype Pollution DoS via Workflow History Compaction","id":"CVE-2026-118678"},"products":["n8n"],"published":"2026-10-28","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["n8n-io"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-118679/"}