{"answers":{"affected":"8 open source packages ship an affected version, including @nuxt/nitro-server and nuxt.","exploited":"There is no known exploitation of CVE-2026-114132 in the wild and no public exploit code.","fix":"Upgrade @nuxt/nitro-server to 4.6.2 or later.","what":"CVE-2026-114132 is a medium-severity vulnerability in nuxt, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114132 and fix it if it is affected.\n\nWhat it is: CVE-2026-114132 is a medium-severity vulnerability in nuxt, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-114132 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @nuxt/nitro-server (npm): affected from 3.20.0; no fix listed\n- @nuxt/nitro-server (npm): affected from 3.20.0; no fix listed\n- @nuxt/nitro-server (npm): affected from 4.2.0; fixed in 4.6.2\n- @nuxt/nitro-server (npm): affected from 4.2.0; fixed in 4.6.2\n- nuxt (npm): affected from 3.0.0; no fix listed\n- nuxt (npm): affected from 3.0.0; no fix listed\n- nuxt (npm): affected from 4.0.0; fixed in 4.6.2\n- nuxt (npm): affected from 4.0.0; fixed in 4.6.2\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-114132/ (Markdown: https://insights.sbomify.com/CVE-2026-114132/index.md)","id":"CVE-2026-114132","markdown":"https://insights.sbomify.com/CVE-2026-114132/index.md","name":"CVE-2026-114132","record":{"aliases":["CLSA-2026-1793181427","CLSA-2026-1793181586","CLSA-2026-1793181946","CLSA-2026-1793182024","GHSA-vjh5-4x84-xrqp"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"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:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-178","name":"Improper Handling of Case Sensitivity"}],"description":"Nuxt is an open-source web development framework for Vue.js. Prior to 4.6.2, Nuxt resolves pages case-insensitively by default while Nitro matches server-side route-rule keys case-sensitively, allowing a request whose path differs only by letter case to render without the server rule intended for that page. The mismatch can skip redirect, headers, proxy, ssr: false, and noScripts, and can cause getRouteRules(event) and matchRouteRules to return no rule for the case variant. Applications that set router.options.sensitive: true in nuxt.config are not affected; setting sensitive only in app/router.options.ts does not establish this exclusion because the server follows the nuxt.config value. Access checks implemented in server middleware, page route middleware, or page data fetching remain independent of this matcher. This issue is fixed in version 4.6.2.","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":"Nuxt: Server-side route rules (`redirect`, `headers`, `proxy`, `ssr`) are skipped for case-variant paths when routing is case-insensitive","id":"CVE-2026-114132","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":8,"n_references":3,"next":{"headline":"Nuxt server islands render `useHeadSafe` input without sanitisation","id":"CVE-2026-114133"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["3.20.0"],"last_affected":[],"package":"@nuxt/nitro-server","purl":null,"source":"GHSA-vjh5-4x84-xrqp"},{"ecosystem":"npm","fixed":[],"introduced":["3.20.0"],"last_affected":[],"package":"@nuxt/nitro-server","purl":"pkg:npm/%40nuxt/nitro-server","source":"GHSA-vjh5-4x84-xrqp"},{"ecosystem":"npm","fixed":["4.6.2"],"introduced":["4.2.0"],"last_affected":[],"package":"@nuxt/nitro-server","purl":null,"source":"GHSA-vjh5-4x84-xrqp"},{"ecosystem":"npm","fixed":["4.6.2"],"introduced":["4.2.0"],"last_affected":[],"package":"@nuxt/nitro-server","purl":"pkg:npm/%40nuxt/nitro-server","source":"GHSA-vjh5-4x84-xrqp"},{"ecosystem":"npm","fixed":[],"introduced":["3.0.0"],"last_affected":[],"package":"nuxt","purl":null,"source":"GHSA-vjh5-4x84-xrqp"},{"ecosystem":"npm","fixed":[],"introduced":["3.0.0"],"last_affected":[],"package":"nuxt","purl":"pkg:npm/nuxt","source":"GHSA-vjh5-4x84-xrqp"},{"ecosystem":"npm","fixed":["4.6.2"],"introduced":["4.0.0"],"last_affected":[],"package":"nuxt","purl":null,"source":"GHSA-vjh5-4x84-xrqp"},{"ecosystem":"npm","fixed":["4.6.2"],"introduced":["4.0.0"],"last_affected":[],"package":"nuxt","purl":"pkg:npm/nuxt","source":"GHSA-vjh5-4x84-xrqp"}],"prev":{"headline":"Nuxt: Route rules are matched against the raw request path, so a percent-encoded segment can bypass `appMiddleware` on dynamic and catch-all routes","id":"CVE-2026-114131"},"products":["nuxt"],"published":"2026-10-21","related":[],"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":"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-10-23","vendors":["nuxt"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114132/"}