Kubernetes Security and Disclosure Information

    Join the group for emails about security and major API announcements.

    We’re extremely grateful for security researchers and users that report vulnerabilities to the Kubernetes Open Source Community. All reports are thoroughly investigated by a set of community volunteers.

    You can also email the private list with the security details and the details expected for all Kubernetes bug reports.

    You may encrypt your email to this list using the GPG keys of the . Encryption using GPG is NOT required to make a disclosure.

    • You think you discovered a potential security vulnerability in Kubernetes
    • You think you discovered a vulnerability in another project that Kubernetes depends on
      • For projects with their own vulnerability reporting and disclosure process, please report it directly there

    When Should I NOT Report a Vulnerability?

    • You need help tuning Kubernetes components for security
    • Your issue is not security related

    Any vulnerability information shared with Security Response Committee stays within Kubernetes project and will not be disseminated to other projects unless it is necessary to get the issue fixed.

    As the security issue moves from triage, to identified fix, to release planning we will keep the reporter updated.