# CVE-2026-118256: Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list - **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 28 Oct 2026 - **Updated:** 28 Oct 2026 - **Also known as:** GHSA-8rc2-428q-7ww3 ## What is CVE-2026-118256? CVE-2026-118256 is a low-severity vulnerability in intlify vue-i18n, published on 28 Oct 2026. ### Official description Vue I18n is the internationalization plugin for Vue.js. From 9.0.0-beta.5 until 11.4.14 and 12.0.0-alpha.5, enabling escapeParameter, called escapeParameterHtml in the Legacy API, does not escape named interpolation values when the same translation call supplies both list and named values because escapeParams() processes only the list branch. Applications that render translations as HTML and pass untrusted named values with a list can insert attacker-controlled markup, including phishing links, forms, and layout changes, and can permit script execution when combined with the srcdoc sanitizer bypass or on releases without the sanitizer. This issue is fixed in versions 11.4.14 and 12.0.0-alpha.5. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-116 (Improper Encoding or Escaping of Output) ## Which versions are affected by CVE-2026-118256? 20 open source packages ship an affected version, including @intlify/vue-i18n-core, @intlify/core and @intlify/core-base. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@intlify/vue-i18n-core` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `@intlify/vue-i18n-core` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `@intlify/vue-i18n-core` | npm | From 9.2.0-alpha.7 | 11.4.14 | | `@intlify/vue-i18n-core` | npm | From 9.2.0-alpha.7 | 11.4.14 | | `@intlify/core` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `@intlify/core` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `@intlify/core` | npm | From 9.0.0-beta.10 | 11.4.14 | | `@intlify/core` | npm | From 9.0.0-beta.10 | 11.4.14 | | `@intlify/core-base` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `@intlify/core-base` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `@intlify/core-base` | npm | From 9.0.0-beta.12 | 11.4.14 | | `@intlify/core-base` | npm | From 9.0.0-beta.12 | 11.4.14 | | `petite-vue-i18n` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `petite-vue-i18n` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `petite-vue-i18n` | npm | From 9.2.0-alpha.7 | 11.4.14 | | `petite-vue-i18n` | npm | From 9.2.0-alpha.7 | 11.4.14 | | `vue-i18n` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `vue-i18n` | npm | From 12.0.0-alpha.1 | 12.0.0-alpha.5 | | `vue-i18n` | npm | From 9.0.0-beta.5 | 11.4.14 | | `vue-i18n` | npm | From 9.0.0-beta.5 | 11.4.14 | ## How do I fix CVE-2026-118256? Upgrade @intlify/vue-i18n-core to a fixed version for your release line: 12.0.0-alpha.5 or 11.4.14. ## Is CVE-2026-118256 being exploited? There is no known exploitation of CVE-2026-118256 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-118256 and fix it if it is affected. What it is: CVE-2026-118256 is a low-severity vulnerability in intlify vue-i18n, published on 28 Oct 2026. Exploitation: There is no known exploitation of CVE-2026-118256 in the wild and no public exploit code. Affected packages and fixed versions: - @intlify/vue-i18n-core (npm): affected from 12.0.0-alpha.1; fixed in 12.0.0-alpha.5 - @intlify/vue-i18n-core (npm): affected from 12.0.0-alpha.1; fixed in 12.0.0-alpha.5 - @intlify/vue-i18n-core (npm): affected from 9.2.0-alpha.7; fixed in 11.4.14 - @intlify/vue-i18n-core (npm): affected from 9.2.0-alpha.7; fixed in 11.4.14 - @intlify/core (npm): affected from 12.0.0-alpha.1; fixed in 12.0.0-alpha.5 - @intlify/core (npm): affected from 12.0.0-alpha.1; fixed in 12.0.0-alpha.5 - @intlify/core (npm): affected from 9.0.0-beta.10; fixed in 11.4.14 - @intlify/core (npm): affected from 9.0.0-beta.10; fixed in 11.4.14 - @intlify/core-base (npm): affected from 12.0.0-alpha.1; fixed in 12.0.0-alpha.5 - @intlify/core-base (npm): affected from 12.0.0-alpha.1; fixed in 12.0.0-alpha.5 - @intlify/core-base (npm): affected from 9.0.0-beta.12; fixed in 11.4.14 - @intlify/core-base (npm): affected from 9.0.0-beta.12; fixed in 11.4.14 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-118256/ (Markdown: https://insights.sbomify.com/CVE-2026-118256/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118256 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118256 - OSV: https://osv.dev/vulnerability/CVE-2026-118256 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-118256/ Summaries are generated and may contain mistakes; the official description above is the record.