CVE-2025-27597
Fix: intlify/vue-i18n@4bb6eacCVE-2025-27597 is a CWE-1321 vulnerability in @intlify/message-resolver. O3 Security confirms whether CVE-2025-27597 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Vue I18n Prototype Pollution in `handleFlatJson`
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@intlify/message-resolvernpm@intlify/vue-i18n-corenpmpetite-vue-i18nnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @intlify/message-resolver | ≥ 9.1.0&&< 9.1.11 | 9.1.11 |
| 📦npm | @intlify/vue-i18n-core | ≥ 9.2.0&&< 9.14.3 | 9.14.3 |
| 📦npm | petite-vue-i18n | ≥ 10.0.0&&< 10.0.6 | 10.0.6 |
| 📦npm | vue-i18n | ≥ 9.1.0&&< 9.14.3 | 9.14.3 |
| 📦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 |
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 CVE-2025-27597 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-27597 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-27597. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-27597 in your dependencies?
O3 detects CVE-2025-27597 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.