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

Go standard library

html/template

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-56858 13 Aug 2026 < 1.25.13; 1.26.0-0 < 1.26.6; 1.27.0-0 < 1.27.0-rc.3 For details on how to apply this update, refer to Ansible Automation Platform documentation. Update reference ↗
CVE-2026-39823 7 May 2026 < 1.25.10; 1.26.0-0 < 1.26.3 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-39826 7 May 2026 < 1.25.10; 1.26.0-0 < 1.26.3 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-32289 8 Apr 2026 < 1.25.9; 1.26.0-0 < 1.26.2 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-27142 6 Mar 2026 < 1.25.8; 1.26.0-0 < 1.26.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-24785 5 Mar 2024 < 1.21.8; 1.22.0-0 < 1.22.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-39319 8 Sep 2023 < 1.20.8; 1.21.0-0 < 1.21.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-2023-39318 8 Sep 2023 < 1.20.8; 1.21.0-0 < 1.21.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-2023-24539 11 May 2023 < 1.19.9; 1.20.0-0 < 1.20.4 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2023-24540 11 May 2023 < 1.19.9; 1.20.0-0 < 1.20.4 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2023-29400 11 May 2023 < 1.19.9; 1.20.0-0 < 1.20.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-2023-24538 6 Apr 2023 < 1.19.8; 1.20.0-0 < 1.20.3 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 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.