Skip to content

Symfony as a CVE Numbering Authority

Symfony is a CVE Numbering Authority (CNA). The CVE Program authorizes us to assign CVE IDs to the vulnerabilities of our projects, and to publish the matching CVE Records. Red Hat is our Root CNA.

We assign CVE IDs to the vulnerabilities of the projects hosted in these GitHub organizations, including their versions that are no longer maintained:

  • symfony, for Symfony, its components and bundles, Symfony UX and Symfony AI, among others;
  • symfony-cli, for the Symfony CLI;
  • symfony-tools, for the tools used to build Symfony;
  • twigphp, for Twig and its extensions;
  • symfonycorp, for the projects of Symfony SAS.

Vulnerabilities of other projects, including the dependencies of our projects, are outside of our scope. Report them to the maintainers of these projects, or to the CNA that covers them.

Send the details to security [at] symfony.com. Use the same address to request a CVE ID, even for a vulnerability that is already public. You can also ask there whether a vulnerability already has one. We don't ask reporters to agree to any terms before handling their request.

When a vulnerability is already public, we answer CVE ID requests within 72 hours.

Our security policy explains how we handle reports. It also lists the issues that we don't consider vulnerabilities, like issues in debug tools that must never run in production.

We follow the CNA Operational Rules of the CVE Program. For example:

  • each vulnerability that can be fixed independently gets a separate CVE ID, even when a single release fixes several vulnerabilities;
  • a vulnerability in code shared by several packages gets a single CVE ID, which lists every affected package;
  • a vulnerability that only affects versions that are no longer maintained still gets a CVE ID, with the unsupported-when-assigned tag;
  • a vulnerability in a dependency keeps the CVE ID of that dependency.

We send the CVE ID to the reporter as soon as we reserve it. When we decide that a report isn't a vulnerability, we explain why to the reporter.

Once the fix is released, each vulnerability gets:

  • a GitHub security advisory, in the repository of the affected project;
  • a post in the Security Advisories category of the Symfony blog;
  • a CVE Record in the CVE List, published within a day of the advisory.

For any CVE ID that we assigned, https://symfony.com/cve-YYYY-NNNNN leads to the matching blog post. The advisories and the CVE Records credit the people who reported and fixed the vulnerability, unless they prefer not to be credited.

If you disagree with one of our decisions, write to security [at] symfony.com and explain why, with any evidence that supports your position. This includes whether a vulnerability exists, how many CVE IDs it needs, and the content of a CVE Record. We handle disputes as the dispute policy of the CVE Program requires:

  • we acknowledge the dispute within three business days;
  • while a dispute that looks legitimate is ongoing, the CVE Record gets the disputed tag;
  • we give our decision within five more business days, or tell you that we need more time;
  • if we need more than 15 business days, you can escalate the dispute to Red Hat, our Root CNA;
  • you can also escalate it if you disagree with our decision.