Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time


Kubernetes Security Release Process and Security Committee documentation.

To report a vulnerability, please refer to

Security Response Committee (SRC)

The Security Response Committee (SRC) is responsible for triaging and handling the security issues for Kubernetes. Following are the current Security Response Committee members:

  • CJ Cullen (@cjcullen) <>
  • Craig Ingram (@cji) <>
  • Joel Smith (@joelsmith) <> [4096R/0x1688ADC79BECDDAF]
  • Luke Hinds (@lukehinds)
  • Micah Hausler (@micahhausler) <>
  • Mo Khan (@enj) <>
  • Rita Zhang (@ritazh)
  • Sri Saran Balaji (@SaranBalaji90) <>
  • Tabitha Sable (@tabbysable) <>

Contacting the SRC

There are a number of contact points for the SRC and release managers in charge of security releases. Please use the correct forum for the best and fastest response.

List or Group Visibility Uses Private Kubernetes security disclosures. This list is closely monitored and triaged by the SRC. See the disclosure guide for full details.
kubernetes-security-discuss Google Group Public Discussion about security disclosure handling, this document, and other updates. Private Release Managers private discussion. All members are subscribed to Private SRC private discussion. All members are subscribed to

Community, discussion, contribution, and support

Learn how to engage with the Kubernetes community on the community page.

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.