Skip to Main Content
ApacheCon is Coming 9-12 Sept. 2019 - Las Vegas The Apache Software Foundation
Apache 20th Anniversary Logo

Community-led development "The Apache Way"

Apache Support Logo


This section is intended to provide guidance to Apache committers on how security vulnerabilities should be handled. The Apache Security Team is available to provide help and advice to Apache projects should it be required.

Publishing information

Projects with known, published vulnerabilities should provide information about those vulnerabilities as part of the project web pages e.g. the httpd security pages. The security information should be clearly linked from the project's homepage.

Security vulnerabilities should not be entered 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 form of, e.g.

When the infrastructure team creates these lists, they are configured so that all messages are automatically copied to If is not, therefore, necessary to cc when sending mail to a project specific security mailing list.

It is expected that a subset of project PMC members and committers will be subscribed to the project specific security mailing list. They are not intended to be used as a third-party notification system and non-committers should not be subscribed to the lists.

Vulnerability handling

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 ahead of time.

Note: this process changed in February 2021 when an internal portal for CVE allocation and submission was introduced

Note: No information should be made public about the vulnerability until it is formally announced at the end of this process. That means, for example that a Jira issue must NOT be created to track the issue since that will make the issue public. Also the 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 the reporting or managing of an undisclosed security vulnerability in Apache software are ignored and no further action is required.

  3. If reported to, the security team will forward the report to the project's security list or, of the project does not have a security list, to the project's private (PMC) mailing list. The security team will respond 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. This e-mail must be cc'd to if it exists, or otherwise.

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

  6. If the report is rejected, the project team writes to the reporter to explain why. This e-mail must be cc'd to if it exists, or otherwise.

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

  8. The project team requests a CVE name from by sending an e-mail with the subject "CVE request for..." and 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 details of the vulnerability can be entered.

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

  11. The project team write up the details of the vulnerability 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 system and no more. Steps to reproduce the vulnerability are not normally included.

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

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

  14. The project team commits the fix. No reference should be made to the commit being related to a security vulnerability.

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

  16. The project team announces the vulnerability. 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.

    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).

    e. The project's security pages should also be updated.

    f. Set the status of the vulerability to 'READY' in the internal portal, this notifies the security team who will then submit the information to the CVE project.

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

  17. The log for the svn commit that applied the fix is updated to include the CVE number. Projects that use git as their primary source code control system should not do this as editing a pushed commit causes all sorts of problems.

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

Information may be shared with domain experts (eg colleagues at your employer) at the discretion of the project's security team providing that it is made clear that the information is not for public disclosure and that or the project's security mailing list must be copied on 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 Mitre have the details of an issue described incorrectly, see the CVE FAQ for how to contact them with corrections.