CVE-2026-118256: Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list

Published Oct 28, 2026
·
Updated

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.

Affected Software

1 affected component
Vue I18n Vue I18n>=9.0.0-beta.5<11.4.14, >=12.0.0-alpha.0<12.0.0-alpha.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Vue I18n to a version that resolves this vulnerability.

    Fixed in 11.4.14
  2. Upgrade

    Upgrade Vue I18n to a version that resolves this vulnerability.

    Fixed in 12.0.0-alpha.5

Event History

Oct 28, 2026
CVE Published
via MITRE·06:20 PM
Data Sourced
via MITRE·06:20 PM
DescriptionWeakness

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications are exposed when they enable escapeParameter (or escapeParameterHtml in the Legacy API), render translations as HTML, and make a translation call that supplies both list and named interpolation values. The named values must be attacker-controlled for markup injection to be possible.

2

What does an attacker need to exploit it?

An attacker needs control of a named interpolation value used in a translation call that also passes list values. In affected calls, the named value is not escaped despite the escapeParameter setting.

3

Does this always result in script execution?

No. The issue can insert attacker-controlled HTML such as phishing links, forms, and layout changes. Script execution may be possible when combined with the srcdoc sanitizer bypass or on releases without the sanitizer.

4

What versions contain a fix?

The issue is fixed in Vue I18n 11.4.14 and 12.0.0-alpha.5.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203