Skip to content

chore: Add CVE template #2752

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
rexagod wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: Add CVE template #2752

rexagod wants to merge 1 commit into from
+32 −0

Conversation

@rexagod
Copy link
Member

@rexagod rexagod commented Aug 28, 2025

In an attempt to reduce the ticket churn we see from third-party detectors.

/cc @mrueg

@k8s-ci-robot k8s-ci-robot requested a review from mrueg August 28, 2025 17:59
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Aug 28, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Aug 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rexagod

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 28, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Aug 28, 2025

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@github-project-automation github-project-automation bot moved this to Needs Triage in SIG Instrumentation Aug 28, 2025
@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 28, 2025
rexagod
rexagod commented Aug 28, 2025
View reviewed changes
.github/ISSUE_TEMPLATE/cve_report.md
name: CVE report
about: Report a CVE detected in kube-state-metrics main branch
title: ''
labels: kind/cve
Copy link
Member Author

@rexagod rexagod Aug 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Introduced a new label to keep CVEs away from kind/bugs categorisation.

@rexagod
chore: Add CVE template
973d7fc 
In an attempt to reduce the ticket churn we see from third-party
detectors.

Signed-off-by: Pranshu Srivastava <[email protected]>
@rexagod rexagod moved this from Needs Triage to Needs Review (PR) or SIG Response (Issue) in SIG Instrumentation Aug 28, 2025
mrueg
mrueg reviewed Sep 1, 2025
View reviewed changes
.github/ISSUE_TEMPLATE/cve_report.md
-->

<!-- `govulncheck` data should include the command ran and should clearly mention the CVE in question in the logs -->

Copy link
Member

@mrueg mrueg Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add a checklist here

Suggested change
[ ] I am aware that output from other scanners is high likely a false positive and the issue will be marked as spam.
[ ] I have verified that govulncheck reports the vulnerability in the latest main

Copy link
Member

@mrueg mrueg Oct 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rexagod do we want to include this?

mrueg
mrueg reviewed Sep 1, 2025
View reviewed changes
.github/ISSUE_TEMPLATE/cve_report.md

* kube-state-metrics version:
* Kubernetes version (use `kubectl version`):
* Cloud provider or hardware configuration:
Copy link
Member

@mrueg mrueg Sep 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this needed for CVEs?

@k8s-triage-robot
Copy link

k8s-triage-robot commented Jan 27, 2026

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 27, 2026
@mrueg
Copy link
Member

mrueg commented Jan 27, 2026

@rexagod still interested?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mrueg mrueg mrueg left review comments

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

SIG Instrumentation
Status: Needs Review (PR) or Response (Issue)

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@rexagod @k8s-ci-robot @k8s-triage-robot @mrueg