@intlify/message-resolver, @intlify/vue-i18n-core: Vue I18n Allows Prototype Pollution in `handleFlatJson`
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- @intlify/message-resolver (npm): from 9.1.0, before 9.1.11
- @intlify/vue-i18n-core (npm): from 9.2.0, before 9.14.3
- petite-vue-i18n (npm): from 10.0.0, before 10.0.6
- vue-i18n (npm): from 9.1.0, before 9.14.3
- @intlify/core-base (npm): from 9.1.0, before 9.1.11
- @intlify/core (npm): from 9.1.0, before 9.1.11
- @intlify/vue-i18n-core (npm): from 10.0.0-alpha.1, before 10.0.6
- @intlify/vue-i18n-core (npm): from 11.0.0-beta.0, before 11.1.2
- petite-vue-i18n (npm): from 11.0.0-beta.0, before 11.1.2
- vue-i18n (npm): from 10.0.0-alpha.1, before 10.0.6
- vue-i18n (npm): from 11.0.0-beta.0, before 11.1.2
The fix
@intlify/message-resolver (npm) fixed in 9.1.11
npmnpm install "@intlify/message-resolver@9.1.11"pnpmpnpm add "@intlify/message-resolver@9.1.11"yarnyarn add "@intlify/message-resolver@9.1.11"bunbun add "@intlify/message-resolver@9.1.11"Check what is installednpm ls @intlify/message-resolverPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @intlify/message-resolver to 9.1.11 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@intlify/vue-i18n-core (npm) fixed in 9.14.3
npmnpm install "@intlify/vue-i18n-core@9.14.3"pnpmpnpm add "@intlify/vue-i18n-core@9.14.3"yarnyarn add "@intlify/vue-i18n-core@9.14.3"bunbun add "@intlify/vue-i18n-core@9.14.3"Check what is installednpm ls @intlify/vue-i18n-corePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @intlify/vue-i18n-core to 9.14.3 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@intlify/vue-i18n-core (npm) fixed in 10.0.6
npmnpm install "@intlify/vue-i18n-core@10.0.6"pnpmpnpm add "@intlify/vue-i18n-core@10.0.6"yarnyarn add "@intlify/vue-i18n-core@10.0.6"bunbun add "@intlify/vue-i18n-core@10.0.6"Check what is installednpm ls @intlify/vue-i18n-corePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @intlify/vue-i18n-core to 10.0.6 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@intlify/vue-i18n-core (npm) fixed in 11.1.2
npmnpm install "@intlify/vue-i18n-core@11.1.2"pnpmpnpm add "@intlify/vue-i18n-core@11.1.2"yarnyarn add "@intlify/vue-i18n-core@11.1.2"bunbun add "@intlify/vue-i18n-core@11.1.2"Check what is installednpm ls @intlify/vue-i18n-corePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @intlify/vue-i18n-core to 11.1.2 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.petite-vue-i18n (npm) fixed in 10.0.6
npmnpm install petite-vue-i18n@10.0.6pnpmpnpm add petite-vue-i18n@10.0.6yarnyarn add petite-vue-i18n@10.0.6bunbun add petite-vue-i18n@10.0.6Check what is installednpm ls petite-vue-i18nPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency petite-vue-i18n to 10.0.6 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.petite-vue-i18n (npm) fixed in 11.1.2
npmnpm install petite-vue-i18n@11.1.2pnpmpnpm add petite-vue-i18n@11.1.2yarnyarn add petite-vue-i18n@11.1.2bunbun add petite-vue-i18n@11.1.2Check what is installednpm ls petite-vue-i18nPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency petite-vue-i18n to 11.1.2 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vue-i18n (npm) fixed in 9.14.3
npmnpm install vue-i18n@9.14.3pnpmpnpm add vue-i18n@9.14.3yarnyarn add vue-i18n@9.14.3bunbun add vue-i18n@9.14.3Check what is installednpm ls vue-i18nPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vue-i18n to 9.14.3 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vue-i18n (npm) fixed in 10.0.6
npmnpm install vue-i18n@10.0.6pnpmpnpm add vue-i18n@10.0.6yarnyarn add vue-i18n@10.0.6bunbun add vue-i18n@10.0.6Check what is installednpm ls vue-i18nPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vue-i18n to 10.0.6 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.vue-i18n (npm) fixed in 11.1.2
npmnpm install vue-i18n@11.1.2pnpmpnpm add vue-i18n@11.1.2yarnyarn add vue-i18n@11.1.2bunbun add vue-i18n@11.1.2Check what is installednpm ls vue-i18nPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency vue-i18n to 11.1.2 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@intlify/core-base (npm) fixed in 9.1.11
npmnpm install "@intlify/core-base@9.1.11"pnpmpnpm add "@intlify/core-base@9.1.11"yarnyarn add "@intlify/core-base@9.1.11"bunbun add "@intlify/core-base@9.1.11"Check what is installednpm ls @intlify/core-basePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @intlify/core-base to 9.1.11 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@intlify/core (npm) fixed in 9.1.11
npmnpm install "@intlify/core@9.1.11"pnpmpnpm add "@intlify/core@9.1.11"yarnyarn add "@intlify/core@9.1.11"bunbun add "@intlify/core@9.1.11"Check what is installednpm ls @intlify/corePaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @intlify/core to 9.1.11 or the nearest later release, to fix CVE-2025-27597. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))