{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-118648 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-118648 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-118648 is a high-severity vulnerability in n8n-io n8n, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-118648 and fix it if it is affected.\n\nWhat it is: CVE-2026-118648 is a high-severity vulnerability in n8n-io n8n, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-118648 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-118648/ (Markdown: https://insights.sbomify.com/CVE-2026-118648/index.md)","id":"CVE-2026-118648","markdown":"https://insights.sbomify.com/CVE-2026-118648/index.md","name":"CVE-2026-118648","record":{"aliases":["GHSA-j6xc-9gw8-942r","GHSA-mp7q-23hg-35cf"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"n8n before 1.123.85, 2.x before 2.43.5, and 2.44.x before 2.44.1 contains a stored cross-site scripting vulnerability because some webhook response paths, such as error responses and responses without headers, omit the sandbox Content-Security-Policy. Authenticated members who can create and activate workflows can serve HTML that runs on the n8n origin, letting scripts act with the session of users who open the webhook URL.","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.85, 2.43.5, and 2.44.1 Stored XSS via Webhook Responses Missing Sandbox Policy","id":"CVE-2026-118648","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"n8n before 2.43.5 and 2.44.1 Authorization Bypass via Crafted Workflow ID in Data Tables","id":"CVE-2026-118649"},"packages":[],"prev":{"headline":"n8n before 1.123.85, 2.43.5, and 2.44.1 SeaTable Trigger API Token Exposure via Execution Data","id":"CVE-2026-118647"},"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-118648/"}