Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY24 SECURITY RECORDS

Strapi

Strapi

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at strapi, 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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-90561 13 Sep 2026 strapi: 4.0.0 ≤ 4.26.2, 5.0.0 < 5.48.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57997 29 Jun 2026 < 5.7.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-2026-27886 14 May 2026 >= 4.0.0, < 5.37.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22707 14 May 2026 < 5.33.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22706 14 May 2026 < 5.33.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22599 14 May 2026 >= 5.0.0, < 5.33.2; >= 4.0.0, < 4.26.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-64526 14 May 2026 < 5.45.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-53092 16 Oct 2025 < 5.20.0 5.20.0. Update reference ↗
CVE-2025-25298 16 Oct 2025 < 5.10.3 5.10.3. Update reference ↗
CVE-2024-56143 16 Oct 2025 >= 5.0.0, < 5.5.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-3930 16 Oct 2025 < 5.24.1 5.24.1. Update reference ↗
CVE-2024-52588 29 May 2025 < 4.25.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-34065 12 Jun 2024 < 4.24.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-31217 12 Jun 2024 < 4.22.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-29181 12 Jun 2024 < 4.19.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-39345 6 Nov 2023 >= 4.0.0, < 4.13.1 4.13.1. Update reference ↗
CVE-2023-38507 15 Sep 2023 < 4.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-37263 15 Sep 2023 < 4.12.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-36472 15 Sep 2023 < 4.11.7 4.11.7. Update reference ↗
CVE-2023-34235 25 Jul 2023 < 4.10.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34093 25 Jul 2023 < 4.10.8 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-2022-29894 13 Jun 2022 v3.x.x versions and earlier No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-30618 19 May 2022 < 3.6.10; < 4.1.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-30617 19 May 2022 < 3.6.9; ! 4.0.0; < 4.0.0-beta.16 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.