---
id: "CVE-2026-118256"
kind: "vulnerability"
aliases: ["CVE-2026-118256", "GHSA-8rc2-428q-7ww3"]
title: "Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list"
severity: "low"
cvss: 2.1
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "vue-i18n", "fixed": ["11.4.14"], "affected": ">= 9.0.0-beta.5, < 11.4.14", "ecosystem": "npm"}, {"name": "vue-i18n", "fixed": ["12.0.0-alpha.5"], "affected": ">= 12.0.0-alpha.1, < 12.0.0-alpha.5", "ecosystem": "npm"}, {"name": "@intlify/core", "fixed": ["11.4.14"], "affected": ">= 9.0.0-beta.10, < 11.4.14", "ecosystem": "npm"}, {"name": "@intlify/core", "fixed": ["12.0.0-alpha.5"], "affected": ">= 12.0.0-alpha.1, < 12.0.0-alpha.5", "ecosystem": "npm"}, {"name": "@intlify/core-base", "fixed": ["11.4.14"], "affected": ">= 9.0.0-beta.12, < 11.4.14", "ecosystem": "npm"}, {"name": "@intlify/core-base", "fixed": ["12.0.0-alpha.5"], "affected": ">= 12.0.0-alpha.1, < 12.0.0-alpha.5", "ecosystem": "npm"}, {"name": "petite-vue-i18n", "fixed": ["11.4.14"], "affected": ">= 9.2.0-alpha.7, < 11.4.14", "ecosystem": "npm"}, {"name": "petite-vue-i18n", "fixed": ["12.0.0-alpha.5"], "affected": ">= 12.0.0-alpha.1, < 12.0.0-alpha.5", "ecosystem": "npm"}, {"name": "@intlify/vue-i18n-core", "fixed": ["11.4.14"], "affected": ">= 9.2.0-alpha.7, < 11.4.14", "ecosystem": "npm"}, {"name": "@intlify/vue-i18n-core", "fixed": ["12.0.0-alpha.5"], "affected": ">= 12.0.0-alpha.1, < 12.0.0-alpha.5", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["cwe-116", "cwe-79", "frontend", "javascript", "package", "vue", "vue-i18n"]
not_affected_if: ["escapeparameter-disabled", "no-user-input-in-translations", "plain-text-output"]
published_at: "2026-10-28T19:17:30+00:00"
first_seen_at: "2026-10-28T19:34:55+00:00"
updated_at: "2026-10-28T21:07:44+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-118256", "first_seen_at": "2026-10-28T19:34:55+00:00"}, {"source": "ghsa", "url": "https://github.com/advisories/GHSA-8rc2-428q-7ww3", "first_seen_at": "2026-10-28T21:07:44+00:00"}]
---

# Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list

When escapeParameter is enabled and a translation call passes both list and named values, named values are not HTML-escaped, so untrusted named values can inject markup into translations rendered as HTML. The sources say this can enable phishing links, forms and script execution when combined with a sanitizer bypass or on releases without the sanitizer.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- npm:vue-i18n affected >= 9.0.0-beta.5, < 11.4.14 fixed 11.4.14
- npm:vue-i18n affected >= 12.0.0-alpha.1, < 12.0.0-alpha.5 fixed 12.0.0-alpha.5
- npm:@intlify/core affected >= 9.0.0-beta.10, < 11.4.14 fixed 11.4.14
- npm:@intlify/core affected >= 12.0.0-alpha.1, < 12.0.0-alpha.5 fixed 12.0.0-alpha.5
- npm:@intlify/core-base affected >= 9.0.0-beta.12, < 11.4.14 fixed 11.4.14
- npm:@intlify/core-base affected >= 12.0.0-alpha.1, < 12.0.0-alpha.5 fixed 12.0.0-alpha.5
- npm:petite-vue-i18n affected >= 9.2.0-alpha.7, < 11.4.14 fixed 11.4.14
- npm:petite-vue-i18n affected >= 12.0.0-alpha.1, < 12.0.0-alpha.5 fixed 12.0.0-alpha.5
- npm:@intlify/vue-i18n-core affected >= 9.2.0-alpha.7, < 11.4.14 fixed 11.4.14
- npm:@intlify/vue-i18n-core affected >= 12.0.0-alpha.1, < 12.0.0-alpha.5 fixed 12.0.0-alpha.5

## How to check

- Check the installed version of `vue-i18n` in the lockfile or with `npm ls vue-i18n`; affected range is 9.0.0-beta.5 up to 11.4.14 and 12.0.0-alpha.5 (not including).
- Search the codebase for `escapeParameter` or `escapeParameterHtml` together with `v-html` or `$t` output rendered as HTML.
- Look for translation calls that pass both a list array and a named object of user-supplied values.

## Fix

- Upgrade `vue-i18n` to `11.4.14` or later (or `12.0.0-alpha.5` for the 12 line).
- Until upgraded, stop passing untrusted named values into HTML-rendered translations or escape them before the call.

## Timeline

- 2026-10-28T19:34:55+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-118256
- 2026-10-28T21:07:44+00:00 ghsa https://github.com/advisories/GHSA-8rc2-428q-7ww3

## From the sources

### Summary

When `escapeParameter` is enabled (`escapeParameterHtml` in the Legacy API), Vue I18n escapes the interpolation parameters before formatting a message. `escapeParams()` escapes either the list values or the named values, but not both: the two branches are joined by `else`. When a single call passes both, for example `t(key, ['...'], { named: { ... } })`, the named values reach the message without being escaped.

### Details

`escapeParams()` in [`packages/core-base/src/translate.ts` (v11.4.13)](https://github.com/intlify/vue-i18n/blob/v11.4.13/packages/core-base/src/translate.ts):

```ts
function escapeParams(options: TranslateOptions) {
  if (isArray(options.list)) {
    options.list = options.list.map(item => (isString(item) ? escapeHtml(item) : item))
  } else if (isObject(options.named)) {
    // ...escapes the named values
  }
}
```

`t(key, list, options)` is a public overload, and `TranslateOptions` has a `named` field, so a call can carry both. The list is checked first, and the named values are then left as they are.

The translated string still goes through `sanitizeTranslatedHtml()` (added for CVE-2025-53892), which neutralizes event handler attributes and `javascript:` URLs. Other markup in the named values, such as links and forms, is inserted as is. Before the fix for GHSA-83rm-6c8r-g728, an `<iframe srcdoc>` in a named value also passes the sanitizer, and script runs. Versions without the sanitizer (before 9.14.5, 10.0.8 and 11.1.10, and 12.0.0-alpha.1 to alpha.3) insert the named values as HTML without any further check.

`<i18n-t>` is not affected: it passes either list or named values, never both, and it does not render translations as HTML.

### PoC

```js
import { createI18n } from 'vue-i18n'

const i18n = createI18n({
  legacy: false,
  locale: 'en',
  escapeParameter: true,
  messages: {
    en: { withList: '{0} {name}', withoutList: '{name}' }
  }
})
const t = i18n.global.t

t('withoutList', { name: '<b>x</b>' })
// &lt;b&gt;x&lt;&#x2F;b&gt;      escaped

t('withList', ['a'], { named: { name: '<b>x</b>' } })
// a <b>x</b>                   not escaped (v11.4.13)
```

### Impact

Applications are affected when they enable `escapeParameter`, render translations as HTML (for example with `v-html`), and pass untrusted named values in the same call as a list. The named values are inserted as markup: phishing links, forms, or layout changes. Together with GHSA-83rm-6c8r-g728, or on versions without the sanitizer, this leads to script execution (DOM-based XSS).

### Patches

Fixed in 11.4.14 and 12.0.0-alpha.5. `escapeParams()` now escapes both the list and the named values.

The fix also stops rewriting the named object that the caller passes. Before, the values of that object were replaced with their escaped form, so a second call with the same object escaped them twice.

v9 and v10 are no longer supported and will not be fixed. Please migrate to v11.

### Workarounds

- Do not pass list and named values in the same call when `escapeParameter` is enabled.
- Do not render translations that can contain untrusted values with `v-html`. Use component interpolation (`<i18n-t>`) instead.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_