← Back
CVE-2025-27597
Vulnerability in @intlify/message-resolver (CVE-2025-27597)
Summary
vulnerability in @intlify/message-resolver (CVE-2025-27597). Risk of unauthorized operations or information disclosure. Exploitable via ``handleFlatJson``. Mitigation: upgrade to `9.1.11` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-27597** has been found in @intlify/message-resolver.
Attackers can target a specific entry point like ``handleFlatJson`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @intlify/message-resolver to **9.1.11** or later.
If unsure, ask your IT team or search "@intlify/message-resolver CVE-2025-27597" on the vendor's site.
CVE-2025-27597 (@intlify/message-resolver) — CWE-1321 /
Attack surface: `handleFlatJson`
Patched: `9.1.11` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-1321) exists in @intlify/message-resolver. Attackers reach the vulnerable code path via ``handleFlatJson`` without authentication.
📍 Affected scope
@intlify/message-resolver — . Attack surface: `handleFlatJson`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **9.1.11**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@intlify/message-resolver' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@intlify/message-resolver' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@intlify/message-resolver` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @intlify/message-resolver to 9.1.11ステージング環境で 9.1.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@intlify/message-resolver
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.1.11"}]}]
npm
@intlify/vue-i18n-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.1.2"}]}]
npm
petite-vue-i18n
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.1.2"}]}]
npm
vue-i18n
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.1.2"}]}]
npm
@intlify/core-base
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.1.11"}]}]
npm
@intlify/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.1.11"}]}]
References
- web https://github.com/intlify/vue-i18n/security/advisories/GHSA-p2ph-7g93-hw3m
- web https://github.com/intlify/vue-i18n/commit/d21e06a7440eed8ada7f522b22fcf830b98d3a53
- web https://github.com/intlify/vue-i18n/commit/fbda9988d3ddd3a1a21740d506d2c183d6b6e36a
- web https://github.com/intlify/vue-i18n/commit/feaf13fcff427f2cb1d5ec8076e639506ba28f9e
- web https://github.com/intlify/vue-i18n/releases/tag/v10.0.6
- web https://github.com/intlify/vue-i18n/releases/tag/v11.1.2
- web https://github.com/intlify/vue-i18n/releases/tag/v9.14.3
- web https://nvd.nist.gov/vuln/detail/CVE-2025-27597
- web https://github.com/intlify/vue-i18n/commit/4bb6eacda7fc2cde5687549afa0efb27ca40862a
- web https://github.com/advisories/GHSA-p2ph-7g93-hw3m