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

librenms

librenms

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-2020-15875 13 Sep 2026 LibreNMS: < 1.65.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-86427 7 Sep 2026 librenms: < 26.8.0 librenms: 26.8.0 Update reference ↗
CVE-2026-86426 7 Sep 2026 librenms: < 26.8.0 librenms: 26.8.0 Update reference ↗
CVE-2026-84194 1 Sep 2026 23.10.0 < 26.4.0 26.4.0 Update reference ↗
CVE-2026-84193 1 Sep 2026 ≤ 26.2.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-84192 1 Sep 2026 < 26.3.1 26.3.1 Update reference ↗
CVE-2026-84191 1 Sep 2026 < 26.5.0 26.5.0 Update reference ↗
CVE-2026-84190 1 Sep 2026 < 26.5.0 26.5.0 Update reference ↗
CVE-2026-84189 1 Sep 2026 < 26.7.0 26.7.0 Update reference ↗
CVE-2026-84188 1 Sep 2026 < 26.7.0 26.7.0 Update reference ↗
CVE-2026-55182 26 Aug 2026 >= 21.6.0, < 26.5.0 26.5.0. Update reference ↗
CVE-2026-45694 26 Aug 2026 < 26.5.0 26.5.0. Update reference ↗
CVE-2026-80214 26 Aug 2026 23.10.0 < 26.4.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-6204 13 Apr 2026 < 26.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2728 13 Apr 2026 < 26.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-26992 20 Feb 2026 < 26.2.0 26.2.0. Update reference ↗
CVE-2026-26991 20 Feb 2026 < 26.2.0 26.2.0. Update reference ↗
CVE-2026-27016 20 Feb 2026 >= 24.10.0, < 26.2.0 26.2.0. Update reference ↗
CVE-2026-26990 20 Feb 2026 < 26.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-2026-26989 20 Feb 2026 < 26.2.0 26.2.0. Update reference ↗
CVE-2026-26988 20 Feb 2026 < 26.2.0 26.2.0. Update reference ↗
CVE-2026-26987 20 Feb 2026 < 26.2.0 26.2.0. Update reference ↗
CVE-2020-36947 27 Jan 2026 1.46 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-68614 22 Dec 2025 < 25.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-65093 18 Nov 2025 < 25.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-65014 18 Nov 2025 < 25.11.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-65013 18 Nov 2025 < 25.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-62412 16 Oct 2025 < 25.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-2025-62411 16 Oct 2025 < 25.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-2025-62365 13 Oct 2025 < 25.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-2025-55296 18 Aug 2025 < 25.8.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-54138 22 Jul 2025 < 25.7.0 25.7.0. Update reference ↗
CVE-2025-47931 17 May 2025 < 25.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-56144 16 Jan 2025 < 24.12.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-23198 16 Jan 2025 < 24.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-23199 16 Jan 2025 < 24.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-23200 16 Jan 2025 < 24.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-23201 16 Jan 2025 < 24.11.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-52526 15 Nov 2024 < 24.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-2024-51497 15 Nov 2024 < 24.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-2024-51496 15 Nov 2024 < 24.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-2024-51495 15 Nov 2024 < 24.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-2024-51494 15 Nov 2024 < 24.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-2024-50355 15 Nov 2024 < 24.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-2024-50352 15 Nov 2024 < 24.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-2024-50351 15 Nov 2024 < 24.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-2024-50350 15 Nov 2024 < 24.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-2024-49764 15 Nov 2024 < 24.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-2024-49759 15 Nov 2024 < 24.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-2024-49758 15 Nov 2024 < 24.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 ↗

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.