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

advplyr

audiobookshelf

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

Lifecycle evidence status

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-73085 11 Aug 2026 < 2.36.0 2.36.0. Update reference ↗
CVE-2026-71209 5 Aug 2026 2.19.1 ≤ 2.35.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42888 11 May 2026 < 2.33.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42887 11 May 2026 < 2.33.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42886 11 May 2026 < 2.33.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42885 11 May 2026 < 2.33.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42884 11 May 2026 < 2.33.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-42883 11 May 2026 < 2.32.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-27963 26 Feb 2026 < 2.32.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-27973 26 Feb 2026 < 2.12.0; < 0.12.0-beta 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-57800 22 Aug 2025 >= 2.6.0, < 2.28.0 2.28.0. Update reference ↗
CVE-2025-46338 29 Apr 2025 < 2.21.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-25205 12 Feb 2025 >= 2.17.0, < 2.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-2024-43797 2 Sep 2024 < 2.13.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2024-35236 27 May 2024 < 2.10.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-51665 27 Dec 2023 < 2.7.0 2.7.0. Update reference ↗
CVE-2023-51697 27 Dec 2023 < 2.7.0 2.7.0. Update reference ↗
CVE-2023-47624 13 Dec 2023 <= 2.4.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-47619 13 Dec 2023 <= 2.4.3 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.