CVSS 3.1
7.2 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NHigh (7.2) in intlify vue-i18n. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in vue-i18n 11.4.14, 12.0.0-alpha.5.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:Nvue-i18n (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/core-base (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/vue-i18n-core (npm): fixed in 11.4.14, 12.0.0-alpha.5@intlify/shared (npm): fixed in 11.4.14, 12.0.0-alpha.5Explain CVE-2026-118257 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118257?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118257?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-118257 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.14.5 |
| intlify vue-i18n | = 10.0.8 |
| intlify vue-i18n | >= 11.1.10, < 11.4.14 |
| intlify vue-i18n | >= 12.0.0-alpha.4, < 12.0.0-alpha.5 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-83rm-6c8r-g728 | npm | vue-i18n | 9.14.5 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | vue-i18n | 10.0.8 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | vue-i18n | >=11.1.10 <11.4.14 | 11.4.14 |
| GHSA-83rm-6c8r-g728 | npm | vue-i18n | >=12.0.0-alpha.4 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
| GHSA-83rm-6c8r-g728 | npm | petite-vue-i18n | 9.14.5 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | petite-vue-i18n | 10.0.8 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | petite-vue-i18n | >=11.1.10 <11.4.14 | 11.4.14 |
| GHSA-83rm-6c8r-g728 | npm | petite-vue-i18n | >=12.0.0-alpha.4 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
| GHSA-83rm-6c8r-g728 | npm | @intlify/core-base | 9.14.5 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | @intlify/core-base | 10.0.8 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | @intlify/core-base | >=11.1.10 <11.4.14 | 11.4.14 |
| GHSA-83rm-6c8r-g728 | npm | @intlify/core-base | >=12.0.0-alpha.4 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
| GHSA-83rm-6c8r-g728 | npm | @intlify/core | 9.14.5 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | @intlify/core | 10.0.8 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | @intlify/core | >=11.1.10 <11.4.14 | 11.4.14 |
| GHSA-83rm-6c8r-g728 | npm | @intlify/core | >=12.0.0-alpha.4 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
| GHSA-83rm-6c8r-g728 | npm | @intlify/vue-i18n-core | 9.14.5 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | @intlify/vue-i18n-core | 10.0.8 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | @intlify/vue-i18n-core | >=11.1.10 <11.4.14 | 11.4.14 |
| GHSA-83rm-6c8r-g728 | npm | @intlify/vue-i18n-core | >=12.0.0-alpha.4 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
| GHSA-83rm-6c8r-g728 | npm | @intlify/shared | 9.14.5 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | @intlify/shared | 10.0.8 | no fix published |
| GHSA-83rm-6c8r-g728 | npm | @intlify/shared | >=11.1.10 <11.4.14 | 11.4.14 |
| GHSA-83rm-6c8r-g728 | npm | @intlify/shared | >=12.0.0-alpha.4 <12.0.0-alpha.5 | 12.0.0-alpha.5 |
Red Hat rates this Moderate.
This vulnerability is evaluated as Moderate severity because successful cross-site scripting requires user interaction alongside specific non-standard application configurations to be exposed. Red Hat products shipping bundled web interfaces using this internationalization library are only susceptible if an application explicitly enables parameter escaping, injects untrusted input into inline frame document attributes, and renders the result as unescaped markup. Standard deployments that avoid dynamic document embedding within localization templates or rely on component-based message interpolation are not exposed to this flaw.
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-118257.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.