CVSS 4.0
2.1 lowCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:NLow (2.1) in intlify vue-i18n. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in vue-i18n 11.4.14, 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:Nvue-i18n (npm): fixed in 11.4.14, 12.0.0-alpha.5@intlify/core (npm): fixed in 11.4.14, 12.0.0-alpha.5@intlify/core-base (npm): fixed in 11.4.14, 12.0.0-alpha.5petite-vue-i18n (npm): fixed in 11.4.14, 12.0.0-alpha.5@intlify/vue-i18n-core (npm): fixed in 11.4.14, 12.0.0-alpha.5Explain CVE-2026-118256 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118256?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118256?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118256 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| intlify vue-i18n | >= 9.0.0-beta.5, < 11.4.14 |
| intlify vue-i18n | >= 12.0.0-alpha.1, < 12.0.0-alpha.5 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-8rc2-428q-7ww3 | npm | vue-i18n | >=9.0.0-beta.5 <11.4.14 | 11.4.14 |
| GHSA-8rc2-428q-7ww3 | npm | vue-i18n | >=12.0.0-alpha.1 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
| GHSA-8rc2-428q-7ww3 | npm | @intlify/core | >=9.0.0-beta.10 <11.4.14 | 11.4.14 |
| GHSA-8rc2-428q-7ww3 | npm | @intlify/core | >=12.0.0-alpha.1 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
| GHSA-8rc2-428q-7ww3 | npm | @intlify/core-base | >=9.0.0-beta.12 <11.4.14 | 11.4.14 |
| GHSA-8rc2-428q-7ww3 | npm | @intlify/core-base | >=12.0.0-alpha.1 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
| GHSA-8rc2-428q-7ww3 | npm | petite-vue-i18n | >=9.2.0-alpha.7 <11.4.14 | 11.4.14 |
| GHSA-8rc2-428q-7ww3 | npm | petite-vue-i18n | >=12.0.0-alpha.1 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
| GHSA-8rc2-428q-7ww3 | npm | @intlify/vue-i18n-core | >=9.2.0-alpha.7 <11.4.14 | 11.4.14 |
| GHSA-8rc2-428q-7ww3 | npm | @intlify/vue-i18n-core | >=12.0.0-alpha.1 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
Red Hat rates this Moderate.
This vulnerability is rated as having a Moderate impact because successful exploitation demands an uncommon set of prerequisites: applications must enable parameter escaping, render translation results directly as raw HTML, and simultaneously pass untrusted user input across both positional and named arguments. In typical Red Hat environments, web interfaces either do not expose the affected execution path or do not combine positional and named interpolation parameters in this manner. Additionally, any resulting impact is restricted to client-side markup injection rather than host or server compromise.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| OpenShift API for Data Protection | oadp/oadp-vmfr-access-filebrowser-rhel9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-118256.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.