← Search results
CVE-LINKED INVENTORY17 SECURITY RECORDS
hedgedoc
hedgedoc
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-58489 | 13 Jul 2026 | < 1.11.0 | 1.11.0. | Update reference ↗ |
| CVE-2026-58486 | 13 Jul 2026 | < 1.11.0 | 1.11.0. | Update reference ↗ |
| CVE-2026-58487 | 13 Jul 2026 | < 1.11.0 | 1.11.0. | Update reference ↗ |
| CVE-2026-58488 | 13 Jul 2026 | < 1.11.0 | 1.11.0. | Update reference ↗ |
| CVE-2026-25642 | 6 Feb 2026 | < 1.10.6 | 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-66629 | 5 Dec 2025 | < 1.10.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-2025-32391 | 10 Apr 2025 | < 1.10.3 | 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-45308 | 2 Sep 2024 | < 1.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-38487 | 4 Aug 2023 | < 1.9.9 | 1.9.9. | Update reference ↗ |
| CVE-2022-24837 | 11 Apr 2022 | >=1.9.1, < 1.9.3 | 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-39175 | 30 Aug 2021 | < 1.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-2021-29503 | 19 May 2021 | < 1.8.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-2021-29474 | 26 Apr 2021 | < 1.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-2021-29475 | 26 Apr 2021 | < 1.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-2021-21259 | 22 Jan 2021 | < 1.7.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-2020-26287 | 28 Dec 2020 | < 1.7.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-2020-26286 | 28 Dec 2020 | < 1.7.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 ↗ |
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.