Commit 42bc9fa485 for bind

commit 42bc9fa485d07cb67e7f5b9b7fb1d30759408e1c
Author: Andoni Duarte Pintado <andoni@isc.org>
Date:   Fri Oct 23 11:20:31 2026 +0200

    Reference the vulnerability matrix step from the CVE checklist

    Previously, the CVE checklist did not mention adding the new releases to
    the Vulnerability Matrix in the Knowledge Base. Make a reference to it
    and point to the release checklist, like other steps shared between the
    two checklists.

diff --git a/.gitlab/issue_templates/Internal_use_only-CVE.md b/.gitlab/issue_templates/Internal_use_only-CVE.md
index 1fa3ede561..2343a631cf 100644
--- a/.gitlab/issue_templates/Internal_use_only-CVE.md
+++ b/.gitlab/issue_templates/Internal_use_only-CVE.md
@@ -90,7 +90,7 @@ confidential!
   - [ ] [:grey_question:][step_clearance]         **(SwEng)** Grant QA & Marketing clearance to proceed with public release
   - [ ] [:grey_question:][step_bump_advisory]     **(Support)** Bump Document Version for the Security Advisory in Printing Press
   - [ ] [:grey_question:][step_publish_advisory]  **(Support)** Knowledge Base: Publish the Security Advisory as a new article
-  - [ ] [:grey_question:][step_matrix]            **(Support)** Knowledge Base: Add the CVE to the full list and (for BIND) the matrix
+  - [ ] [:grey_question:][step_matrix]            **(Support)** Knowledge Base: Add the CVE to the full list and (for BIND) the matrix. Also add the new releases to the vulnerability matrix (as outlined in the release checklist)
   - [ ] [:grey_question:][step_publish]           **(QA/Marketing)** Publish the releases (as outlined in the release checklist)
   - [ ] [:grey_question:][step_notifications]     **(QA)** Send notification emails to third parties
   - [ ] [:grey_question:][step_mitre]             **(QA)** Advise MITRE about the disclosed CVEs