CVE-2026-118256: Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list
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.
Published Oct 28, 2026
Affected packages
vue-i18n
- Ecosystem
- npm
- Affected
- >= 9.0.0-beta.5, < 11.4.14
- Fixed in
- 11.4.14
- Check
npm ls vue-i18n
vue-i18n
- Ecosystem
- npm
- Affected
- >= 12.0.0-alpha.1, < 12.0.0-alpha.5
- Fixed in
- 12.0.0-alpha.5
- Check
npm ls vue-i18n
@intlify/core
- Ecosystem
- npm
- Affected
- >= 9.0.0-beta.10, < 11.4.14
- Fixed in
- 11.4.14
- Check
npm ls @intlify/core
@intlify/core
- Ecosystem
- npm
- Affected
- >= 12.0.0-alpha.1, < 12.0.0-alpha.5
- Fixed in
- 12.0.0-alpha.5
- Check
npm ls @intlify/core
@intlify/core-base
- Ecosystem
- npm
- Affected
- >= 9.0.0-beta.12, < 11.4.14
- Fixed in
- 11.4.14
- Check
npm ls @intlify/core-base
@intlify/core-base
- Ecosystem
- npm
- Affected
- >= 12.0.0-alpha.1, < 12.0.0-alpha.5
- Fixed in
- 12.0.0-alpha.5
- Check
npm ls @intlify/core-base
petite-vue-i18n
- Ecosystem
- npm
- Affected
- >= 9.2.0-alpha.7, < 11.4.14
- Fixed in
- 11.4.14
- Check
npm ls petite-vue-i18n
petite-vue-i18n
- Ecosystem
- npm
- Affected
- >= 12.0.0-alpha.1, < 12.0.0-alpha.5
- Fixed in
- 12.0.0-alpha.5
- Check
npm ls petite-vue-i18n
@intlify/vue-i18n-core
- Ecosystem
- npm
- Affected
- >= 9.2.0-alpha.7, < 11.4.14
- Fixed in
- 11.4.14
- Check
npm ls @intlify/vue-i18n-core
@intlify/vue-i18n-core
- Ecosystem
- npm
- Affected
- >= 12.0.0-alpha.1, < 12.0.0-alpha.5
- Fixed in
- 12.0.0-alpha.5
- Check
npm ls @intlify/vue-i18n-core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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):
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
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: 'x' })
// <b>x</b> escaped
t('withList', ['a'], { named: { name: 'x' } })
// a x 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
escapeParameteris enabled. - Do not render translations that can contain untrusted values with
v-html. Use component interpolation (<i18n-t>) instead.
References
- https://github.com/intlify/vue-i18n/security/advisories/GHSA-8rc2-428q-7ww3
- https://github.com/intlify/vue-i18n/pull/2680
- https://github.com/intlify/vue-i18n/commit/d657ce8f4b3b6b198a8f6e3d09e2b57a5d019fb8
- https://github.com/intlify/vue-i18n/releases/tag/v11.4.14
- https://github.com/intlify/vue-i18n/releases/tag/v12.0.0-alpha.5
- https://github.com/advisories/GHSA-8rc2-428q-7ww3
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-118257
Vue I18n: escapeParameter does not prevent XSS through srcdoc in translation messages
high7.2No fixOct 28, 2026CVE-2025-53892
vue-i18n's escapeParameterHtml does not prevent DOM-based XSS through its tag attributes
medium5.3Jul 16, 2025CVE-2025-27597
Vue I18n Allows Prototype Pollution in `handleFlatJson`
high8.9Mar 7, 2025CVE-2024-52809
vue-i18n has cross-site scripting vulnerability with prototype pollution
medium5.3Dec 2, 2024CVE-2024-52810
@intlify/shared Prototype Pollution vulnerability
medium6.9Dec 2, 2024
