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

dgtlmoon

Changedetection.io

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-95657 22 Sep 2026 Changedetection.io: 0.55.0, 0.55.1, 0.55.2, 0.55.3, 0.55.4, 0.55.5, 0.55.6, 0.55.7, 0.55.8 Changedetection.io: 0.60.1 Update reference ↗
CVE-2026-95656 22 Sep 2026 changedetection.io: 50389b07 changedetection.io: 0.60.1 Update reference ↗
CVE-2026-95273 22 Sep 2026 changedetection.io: 0.60.0, 0.60.1, 0.60.2, 0.60.3, 0.60.4, 0.60.5, 0.60.6, 0.60.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-95272 22 Sep 2026 changedetection.io: 0.60.0, 0.60.1, 0.60.2, 0.60.3, 0.60.4, 0.60.5, 0.60.6, 0.60.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-95271 22 Sep 2026 changedetection.io: 0.60.0, 0.60.1, 0.60.2, 0.60.3, 0.60.4, 0.60.5, 0.60.6, 0.60.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-95270 22 Sep 2026 changedetection.io: 0.60.0, 0.60.1, 0.60.2, 0.60.3, 0.60.4, 0.60.5, 0.60.6, 0.60.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-92815 16 Sep 2026 changedetection.io: ≤ 0.60.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-92814 16 Sep 2026 changedetection.io: ≤ 0.60.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-71205 5 Aug 2026 0.55.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-71204 5 Aug 2026 0.55.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-71203 5 Aug 2026 0.55.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-43891 12 May 2026 < 0.55.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-41895 12 May 2026 <= 0.54.9 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-35490 7 Apr 2026 < 0.54.8 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-35000 1 Apr 2026 < 0.54.7 dadc804567a51f803cd6715f7885c11a247915f6 Update reference ↗
CVE-2026-33981 27 Mar 2026 < 0.54.7 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-29065 6 Mar 2026 < 0.54.4 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-29039 6 Mar 2026 < 0.54.4 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-29038 6 Mar 2026 < 0.54.4 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-27696 25 Feb 2026 < 0.54.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-2026-27645 25 Feb 2026 < 0.54.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-2026-25527 19 Feb 2026 < 0.53.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-62780 10 Nov 2025 < 0.50.34 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-52558 23 Jun 2025 < 0.50.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-56509 27 Dec 2024 < 0.48.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-51998 7 Nov 2024 < 0.47.06 0.47.06 Update reference ↗
CVE-2024-51483 1 Nov 2024 < 0.47.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-34061 2 May 2024 < 0.45.22 0.45.22. Update reference ↗
CVE-2024-32651 25 Apr 2024 <= 0.45.20 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23329 19 Jan 2024 >= 0.39.14, < 0.45.13 0.45.13. 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.