CVE-2025-27597 json
Vue I18n Prototype Pollution in `handleFlatJson`
published 2025-03-07 20 mo ago modified 2026-08-26 2 mo ago also GHSA-p2ph-7g93-hw3m , EUVD-2025-7792
- cvss
- 8.9
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm @intlify/message-resolver 9.1.11
- npm @intlify/vue-i18n-core 9.14.3, 10.0.6, 11.1.2
- npm petite-vue-i18n 10.0.6, 11.1.2
- npm vue-i18n 9.14.3, 10.0.6, 11.1.2
- npm @intlify/core-base 9.1.11
- npm @intlify/core 9.1.11
- github.com/intlify/vue-i18n@4bb6eac commit
- github.com/intlify/vue-i18n@d21e06a commit
- github.com/intlify/vue-i18n@fbda998 commit
- github.com/intlify/vue-i18n@feaf13f commit
- github.com/intlify/vue-i18n/releases/tag/v10.0.6 release
- github.com/intlify/vue-i18n/releases/tag/v11.1.2 release
- github.com/intlify/vue-i18n/releases/tag/v9.14.3 release
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 20 mo ago
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/intlify/vue-i18n/security/advisories/GHSA-p2ph-7g93-hw3m referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 4.0 | 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @intlify/message-resolver | >=9.1.0, <9.1.11 |
9.1.11 |
| npm | @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 | petite-vue-i18n | >=10.0.0, <10.0.6 >=11.0.0-beta.0, <11.1.2 |
10.0.6 11.1.2 |
| npm | 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 |
| npm | @intlify/core-base | >=9.1.0, <9.1.11 |
9.1.11 |
| npm | @intlify/core | >=9.1.0, <9.1.11 |
9.1.11 |
Affected products
- intlify vue-i18n
Classification
- Weakness
-
- CWE-1321 Improperly Controlled Modification of Object Prototype Attributes
References
-
github.com
/intlify/vue-i18n/commit/4bb6eacda7fc2cde5687549afa0efb27ca40862a
web
-
github.com
/intlify/vue-i18n/commit/d21e06a7440eed8ada7f522b22fcf830b98d3a53
web
-
github.com
/intlify/vue-i18n/commit/fbda9988d3ddd3a1a21740d506d2c183d6b6e36a
web
-
github.com
/intlify/vue-i18n/commit/feaf13fcff427f2cb1d5ec8076e639506ba28f9e
web
-
github.com
/intlify/vue-i18n/security/advisories/GHSA-p2ph-7g93-hw3m
exploit, web
-
nvd.nist.gov
/vuln/detail/CVE-2025-27597
advisory
-
github.com
/intlify/vue-i18n
package
-
github.com
/intlify/vue-i18n/releases/tag/v10.0.6
web
-
github.com
/intlify/vue-i18n/releases/tag/v11.1.2
web
-
github.com
/intlify/vue-i18n/releases/tag/v9.14.3
web
Sources
- CVE List CVE-2025-27597
- GitHub Advisory GHSA-p2ph-7g93-hw3m
- NVD CVE-2025-27597
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.