# CVE-2025-27597: Vue I18n Prototype Pollution in `handleFlatJson` > Attackers can exploit prototype pollution in Vue I18n to cause denial of service or potentially execute arbitrary code via sensitive Node.js APIs. - **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Mar 2025 - **Updated:** 7 Mar 2025 - **Also known as:** GHSA-p2ph-7g93-hw3m ## What is CVE-2025-27597? CVE-2025-27597 is a high-severity code injection vulnerability in intlify vue-i18n, published on 7 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Vue I18n is the internationalization plugin for Vue.js. @intlify/message-resolver and @intlify/vue-i18n-core are vulnerable to Prototype Pollution through the entry function: handleFlatJson. An attacker can supply a payload with Object.prototype setter to introduce or modify properties within the global prototype chain, causing denial of service (DoS) a the minimum consequence. Moreover, the consequences of this vulnerability can escalate to other injection-based attacks, depending on how the library integrates within the application. For instance, if the polluted property propagates to sensitive Node.js APIs (e.g., exec, eval), it could enable an attacker to execute arbitrary commands within the application's context. Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes) ## Which versions are affected by CVE-2025-27597? 22 open source packages ship an affected version, including @intlify/vue-i18n-core, @intlify/core and @intlify/core-base. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@intlify/vue-i18n-core` | npm | From 10.0.0-alpha.1 | 10.0.6 | | `@intlify/vue-i18n-core` | npm | From 10.0.0-alpha.1 | 10.0.6 | | `@intlify/vue-i18n-core` | npm | From 11.0.0-beta.0 | 11.1.2 | | `@intlify/vue-i18n-core` | npm | From 11.0.0-beta.0 | 11.1.2 | | `@intlify/vue-i18n-core` | npm | From 9.2.0 | 9.14.3 | | `@intlify/vue-i18n-core` | npm | From 9.2.0 | 9.14.3 | | `@intlify/core` | npm | From 9.1.0 | 9.1.11 | | `@intlify/core` | npm | From 9.1.0 | 9.1.11 | | `@intlify/core-base` | npm | From 9.1.0 | 9.1.11 | | `@intlify/core-base` | npm | From 9.1.0 | 9.1.11 | | `@intlify/message-resolver` | npm | From 9.1.0 | 9.1.11 | | `@intlify/message-resolver` | npm | From 9.1.0 | 9.1.11 | | `petite-vue-i18n` | npm | From 10.0.0 | 10.0.6 | | `petite-vue-i18n` | npm | From 10.0.0 | 10.0.6 | | `petite-vue-i18n` | npm | From 11.0.0-beta.0 | 11.1.2 | | `petite-vue-i18n` | npm | From 11.0.0-beta.0 | 11.1.2 | | `vue-i18n` | npm | From 10.0.0-alpha.1 | 10.0.6 | | `vue-i18n` | npm | From 10.0.0-alpha.1 | 10.0.6 | | `vue-i18n` | npm | From 11.0.0-beta.0 | 11.1.2 | | `vue-i18n` | npm | From 11.0.0-beta.0 | 11.1.2 | | `vue-i18n` | npm | From 9.1.0 | 9.14.3 | | `vue-i18n` | npm | From 9.1.0 | 9.14.3 | ## How do I fix CVE-2025-27597? Upgrade @intlify/vue-i18n-core to a fixed version for your release line: 10.0.6, 11.1.2 or 9.14.3. ## Is CVE-2025-27597 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27597 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-27597 and fix it if it is affected. What it is: CVE-2025-27597 is a high-severity code injection vulnerability in intlify vue-i18n, published on 7 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27597 exists. Affected packages and fixed versions: - @intlify/vue-i18n-core (npm): affected from 10.0.0-alpha.1; fixed in 10.0.6 - @intlify/vue-i18n-core (npm): affected from 10.0.0-alpha.1; fixed in 10.0.6 - @intlify/vue-i18n-core (npm): affected from 11.0.0-beta.0; fixed in 11.1.2 - @intlify/vue-i18n-core (npm): affected from 11.0.0-beta.0; fixed in 11.1.2 - @intlify/vue-i18n-core (npm): affected from 9.2.0; fixed in 9.14.3 - @intlify/vue-i18n-core (npm): affected from 9.2.0; fixed in 9.14.3 - @intlify/core (npm): affected from 9.1.0; fixed in 9.1.11 - @intlify/core (npm): affected from 9.1.0; fixed in 9.1.11 - @intlify/core-base (npm): affected from 9.1.0; fixed in 9.1.11 - @intlify/core-base (npm): affected from 9.1.0; fixed in 9.1.11 - @intlify/message-resolver (npm): affected from 9.1.0; fixed in 9.1.11 - @intlify/message-resolver (npm): affected from 9.1.0; fixed in 9.1.11 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-27597/ (Markdown: https://insights.sbomify.com/CVE-2025-27597/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27597 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27597 - OSV: https://osv.dev/vulnerability/CVE-2025-27597 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-27597/ Summaries are generated and may contain mistakes; the official description above is the record.