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

gohugoio

hugo

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-100694 26 Sep 2026 hugo: 0.56.0 < 0.166.0 hugo: 0.166.0 Update reference ↗
CVE-2026-100693 26 Sep 2026 hugo: 0.162.0 < 0.166.0 hugo: 0.166.0 Update reference ↗
CVE-2026-100692 26 Sep 2026 hugo: < 0.166.0 hugo: 0.166.0 Update reference ↗
CVE-2026-100691 26 Sep 2026 hugo: 0.75.0 < 0.166.0 hugo: 0.166.0 Update reference ↗
CVE-2026-100690 26 Sep 2026 hugo: 0.161.0 < 0.166.0 hugo: 0.166.0 Update reference ↗
CVE-2026-89259 11 Sep 2026 hugo: < 0.165.0 hugo: 0.165.0 Update reference ↗
CVE-2026-89258 11 Sep 2026 < 0.165.0 0.165.0 Update reference ↗
CVE-2026-10618 24 Aug 2026 hugo: 0.93.0 ≤ 0.165.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-10582 24 Aug 2026 hugo: 0.91.0 ≤ 0.165.0 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Update reference ↗
CVE-2026-75926 18 Aug 2026 hugo: 0.162.0 < 0.165.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-50135 6 Jul 2026 >= 0.123.0, < 0.162.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-50134 6 Jul 2026 >= 0.91.0, < 0.162.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-50133 6 Jul 2026 < 0.162.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-58403 6 Jul 2026 >= 0.123.0, < 0.163.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-58402 6 Jul 2026 >= 0.60.0, < 0.163.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-2026-58404 6 Jul 2026 >= v0.162.0, < v0.163.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-44301 12 May 2026 >= 0.43.0, < 0.161.0 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-35166 6 Apr 2026 >= 0.60.0, < 0.159.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-55601 9 Dec 2024 >= 0.123.0, < 0.139.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-32875 23 Apr 2024 >= 0.123.0, < 0.125.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26284 21 Dec 2020 < 0.79.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.