Description
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.
Recommendation
Update the petite-vue-i18n package to the latest compatible version. Followings are version details:
Affected version(s): **>= 12.0.0-alpha.1, < 12.0.0-alpha.5 >= 9.2.0-alpha.7, < 11.4.14** Patched version(s): **12.0.0-alpha.5 11.4.14**
References
Could your website be exposed too?
SmartScanner can check your website for Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list and gives you actionable findings to investigate.
Start a free scanRelated Issues
- Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list - @intlify/core - CVE-2026-118256
- Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list - @intlify/vue-i18n-core - CVE-2026-118256
- Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list - @intlify/core-base - CVE-2026-118256
- Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list - vue-i18n - CVE-2026-118256


