Page History

As you can read in the Security Process, security reports must be handled in private by the PMC. You should not create a public Jira ticket to track the issue, or a public GitHub issue, since those would make the issue public. Messages associated with any commits should not make any reference to the security nature of the commit. The first point that any information regarding the vulnerability is made public is when the advisory is published after the release with the fix has been announced. See Working In Private for more notes on how to do this in practice.

Nonetheless, the PMC can ask for help in handling security issues: if the PMC does not have the bandwidth to handle issues within a reasonable time, or if they want to ask the help of a trusted community member or outside subject matter expert, they can share information about the report in private on a one-on-one need-to-know basis. As with all communication around security issues, it is recommended to Cc security@apache.org in the exchange. Of course, it should be clear that you expect them to keep the shared information private.

...

If your project handles many security reports, it can be helpful to introduce a private security@<project>.apache.org mailinglist. If such a list exists, security reports will be sent to this list instead of to the PMC, and the ASF Security Team will no longer respond with a 'receipt confirmation' to the reporter - this is now your responsibility. The list should contain have enough PMC members to make sure the project can responsibly deal with any incoming security reports. You can also add trusted committers to this list, if they for some reason cannot or don't want to join the PMCmessages about security issues responsibly and timely.

How you as PMC invite and rotate the members of your security team is up to you to decide. For inspiration, you could have a look at how the Airflow PMC has arranged this. For example, it is encouraged to periodically rotate out participants from outside the PMC that are not actively contributing.

...