CVE-2026-118256: low-severity vulnerability in intlify vue-i18n
Vue I18n: `escapeParameter` does not escape named values when the same call also passes a list
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 2.1epss 0.5%
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.
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
Affected products
intlify · vue-i18nRelated CVEs — intlify vue-i18n
In the same product, most dangerous first.
CVE-2025-53892MEDIUMIntlify Vue I18n's escapeParameterHtml does not prevent DOM-based XSS via tag attributes like onerrorEPSS 0.8%CVE-2024-52810MEDIUMPrototype Pollution in @intlify/shared >=9.7.0 <= 10.0.4EPSS 0.8%CVE-2024-52809MEDIUMCross-site Scripting vulnerability with prototype pollution in vue-i18nEPSS 0.7%CVE-2025-27597HIGHVue I18n Prototype Pollution in `handleFlatJson`EPSS 0.6%CVE-2026-118257HIGHVue I18n: escapeParameter does not prevent XSS through srcdoc in translation messagesEPSS 0.3%