Skip to Main Content
ApacheCon 2021 Coming Soon! The Apache Software Foundation
Apache 20th Anniversary Logo

Community-led development "The Apache Way"

Apache Support Logo


This section provides guidance to Apache committers on how to handle security vulnerabilities. The Apache Security Team is available to provide help and advice to Apache projects should you require it.

Publishing information

Projects with known, published vulnerabilities should provide information about those vulnerabilities on pages such as the httpd security pages. Provide a clear link on the project's home page to The security information.

Do not enter details of security vulnerabilities in a project's public bug tracker unless the necessary configuration is in place to limit access to the issue to only the reporter and the project team.

Project specific security mailing lists

Projects may also wish to create a project-specific security mailing list. These take the name in the form, like

When the infrastructure team creates these lists, they configure them to automatically copy all messages to If is not, therefore, necessary to cc when sending mail to a project-specific security mailing list.

We expect that a subset of project PMC members and committers will subscribe to the project-specific security mailing list. Do not use the list as a third-party notification system; non-committers should not be subscribed to the lists.

Handling a possible vulnerability

A typical process for handling a new security vulnerability is as follows. Projects that wish to use other processes may do so, but must clearly and publicly document their process and have security@ review it before they begin using it.

Note: this process changed in February 2021, when an internal portal for CVE allocation and submission became available.

Note: Do not make information about the vulnerability public until it isformally announced at the end of this process. That means, for example, that you should NOT create a Jira ticket to track the issue, since that would make the issue public. Messages associated with any commits should not make ANY reference to the security nature of the commit.

  1. The person discovering the issue, the reporter, reports the vulnerability privately to or to

  2. Messages that do not relate to reporting or managing an undisclosed security vulnerability in Apache software are ignored and no further action is required.

  3. If the report comes to, the security team forwards it to the project's security list or, if the project does not have a security list, to the project's private (PMC) mailing list. The security team responds to the original reporter that this has been done.

  4. The project team sends an e-mail to the original reporter to acknowledge the report, with a copy to if it exists, or

  5. The project team investigates the report and either rejects or accepts it.

  6. If the project team rejects the report, the team writes to the reporter to explain why, with a copy to if it exists, or to

  7. If the project team accepts the report, the team writes to the reporter to let them know that they have accepted the report and that they are working on a fix.

  8. The project team requests a CVE (Common Vulnerabilites and Exposures) name from the internal portal, Alternatively by sending an e-mail with the subject "CVE request for..." to, providing a short (one-line) description of the vulnerability. can help determine if a report requires multiple CVEs or if multiple reports should be merged under a single CVE.

  9. The ASF security team will allocate a CVE and send a link to the internal portal where the project team can enter details of the vulnerability.

  10. The project team agrees on a fix on their private list.

  11. The project team writes up the details of the vulnerability and the fix on the internal portal. The portal generates draft announcement texts. For an example of an announcement see Tomcat's announcement of CVE-2008-2370. The level of detail to include in the report is a matter of judgement. Generally, reports should contain enough information to enable people to assess the risk associated with the vulnerability for their own system, and no more. Announcments do not normally include steps to reproduce the vulnerability.

  12. The project team provides the reporter with a copy of the fix and the draft vulnerability announcement for comment.

  13. The project team agrees on the fix, the announcement and the release schedule with the reporter.

  14. The project team commits the fix. Do not make any reference that the commit relates to a security vulnerability.

  15. The project team creates a release that includes the fix.

  16. The project team announces the vulnerability and the fix. The vulnerability announcement should be sent after, or at the same time as, the release announcement to the following destinations. The internal portal generates texts that can be used for the emails and can send the emails if required.

    a. the same destinations as the release announcement

    b. the vulnerability reporter

    c. the project's security list (or if the project does not have a dedicated security list)

    d. (subscription not required).

  17. The project team updates the project's security pages.

  18. Set the status of the vulerability to 'READY' in the internal portal. This notifies the security team, which will submit the information to the CVE project.

    This is the first point that any information regarding the vulnerability is made public.

  19. If the project repository is in Subversion, add the CVE number to the log for the commit that applied the fix. Do not try to do this if your project uses a Git repository, as editing a pushed commit causes all sorts of problems.

If the project does not have a dedicated mailing list, copy all communication regarding the vulnerability to There is no need to do this for messages sent to since these are automatically copied to

Share information about the vulnerability with domain experts (or colleagues at your employer) at the discretion of the project's security team, providing that you make clear that the information is not for public disclosure and that you copy to or the project's security mailing list any communication regarding the vulnerability.

CVE names

Common Vulnerabilities and Exposures (CVE) IDs are a unique identifiers given to security flaws. The Apache Security Team is a CVE Numbering Authority (CNA) covering all Apache projects and is the only group able to allocate names to Apache Software Foundation project issues.

If you believe the details of an issue are described incorrectly, see the CVE FAQ for how to contact Mitre, the CVE organization, with corrections.