← Search results
CVE-LINKED INVENTORY34 SECURITY RECORDS
misskey-dev
misskey
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
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-2026-46714 | 3 Aug 2026 | >= 8.63.0, < 2026.5.4 | 2026.5.4. | Update reference ↗ |
| CVE-2026-47746 | 3 Aug 2026 | >= 12.37.0, < 2026.5.4 | 2026.5.4. | Update reference ↗ |
| CVE-2026-46713 | 3 Aug 2026 | >= 12.37.0, < 2026.5.4 | 2026.5.4. | Update reference ↗ |
| CVE-2026-46712 | 3 Aug 2026 | >= 2025.3.2, < 2026.5.4 | 2026.5.4. | Update reference ↗ |
| CVE-2026-48115 | 3 Aug 2026 | >= 2024.5.0, < 2026.5.4 | 2026.5.4. | Update reference ↗ |
| CVE-2026-57574 | 10 Jul 2026 | < 2026.6.0 | 2026.6.0. | Update reference ↗ |
| CVE-2026-57575 | 10 Jul 2026 | < 2026.6.0 | 2026.6.0. | Update reference ↗ |
| CVE-2026-28433 | 9 Mar 2026 | >= 10.93.0, < 2026.3.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-28432 | 9 Mar 2026 | < 2026.3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-28431 | 9 Mar 2026 | >= 8.45.0, < 2026.3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66482 | 15 Dec 2025 | >= 2025.9.1, < 2025.12.0-alpha.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-66402 | 15 Dec 2025 | >= 13.0.0-beta.16, < 2025.12.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-46559 | 5 May 2025 | >= 12.31.0, < 2025.4.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-46340 | 5 May 2025 | >= 12.0.0, < 2025.4.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-25306 | 10 Mar 2025 | < 2025.2.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-24897 | 11 Feb 2025 | >= 12.109.0, < 2025.2.0-alpha.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-24896 | 11 Feb 2025 | >= 12.109.0, < 2025.2.0-alpha.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-49363 | 18 Dec 2024 | < CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H | 2024.11.0-alpha.3. | Update reference ↗ |
| CVE-2024-52579 | 18 Dec 2024 | < 2024.11.0-alpha.3 | 2024.11.0-alpha.3. | Update reference ↗ |
| CVE-2024-52590 | 18 Dec 2024 | >= 2024.8.0-rc.3, < 2024.11.0-alpha.3 | 2024.11.0-alpha.3. | Update reference ↗ |
| CVE-2024-52591 | 18 Dec 2024 | < 2024.11.0-alpha.3 | 2024.11.0-alpha.3. | Update reference ↗ |
| CVE-2024-52592 | 18 Dec 2024 | >= 10.92.1, < 2024.11.0-alpha.3 | 2024.11.0-alpha.3. | Update reference ↗ |
| CVE-2024-52593 | 18 Dec 2024 | >= 12.29.0, < 2024.11.0-alpha.3 | 2024.11.0-alpha.3. | Update reference ↗ |
| CVE-2024-32983 | 3 Jun 2024 | < 2024.5.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-25636 | 19 Feb 2024 | < 2024.2.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-52139 | 29 Dec 2023 | < 2023.12.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-49079 | 29 Nov 2023 | < 2023.11.1-beta.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-43793 | 4 Oct 2023 | < 2023.9.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-24810 | 22 Feb 2023 | < 13.3.1 | 13.3.1. | Update reference ↗ |
| CVE-2023-24811 | 22 Feb 2023 | < 13.3.2 | 13.3.2. | Update reference ↗ |
| CVE-2023-24812 | 22 Feb 2023 | < 13.3.3 | 13.3.3. | Update reference ↗ |
| CVE-2023-25154 | 22 Feb 2023 | < 13.5.0 | 13.5.0. | Update reference ↗ |
| CVE-2021-39195 | 7 Sep 2021 | < 12.90.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-39169 | 27 Aug 2021 | < 12.51.0 | 12.51.0. | Update reference ↗ |
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.