intlify
vue-i18n
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at vue-i18n, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2025-53892 | 16 Jul 2025 | >= 9.0.0, < 9.14.5; >= 10.0.0, < 10.0.8; >= 11.0.0, < 11.1.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27597 | 7 Mar 2025 | >= 9.1.0, < 9.14.3; >= 10.0.0-alpha.1, < 10.0.6; >= 11.0.0-beta.0, < 11.1.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-52810 | 29 Nov 2024 | >= 9.7.0, < 9.14.2; >= 10.0.0, < 10.0.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-52809 | 29 Nov 2024 | < 9.14.2; >= 10.0.0, < 10.0.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.