Symfony Takes Direct Control of CVE IDs for Its Projects
- Nicolas Grekas
- 766 reads
Symfony will assign CVE IDs when it publishes vulnerability advisories, with records following within a day. Its scope covers five GitHub organizations.


Symfony will now assign CVE identifiers for vulnerabilities in projects it maintains and publish the matching records itself. The change puts the project in a position to give each advisory an identifier on publication day, instead of waiting on an outside party to provide one.
The CVE Program has added Symfony as a CVE Numbering Authority, with Red Hat serving as its Root CNA. A CVE identifier gives a vulnerability a standard reference that can be used across advisories and security databases. For teams managing software dependencies, that identifier helps connect a vendor’s notice to vulnerability records and internal tracking systems.
Faster identifiers, clearer timing
Previously, Symfony requested CVE IDs for its advisories from GitHub. Those requests could take weeks. In recent months, Checkmarx helped assign IDs: high severity issues received identifiers in time for their releases, while other IDs arrived a few days later.
Symfony says the new process changes that timing. Each advisory will have a CVE ID on the day it is published, and its corresponding CVE Record is expected within a day. That gives maintainers and users a more predictable reference point when a fix becomes public. It also reduces the gap between an advisory’s publication and the appearance of its record in the CVE system.
The practical value is in coordination. Engineering teams often need to match a vulnerability notice to affected software versions, decide whether a deployed component is exposed, and follow remediation across repositories or products. A stable identifier makes those tasks easier to organize, especially when the same issue appears in several tracking tools. The identifier itself doesn’t fix a vulnerability or replace the technical details of an advisory; it gives those details a consistent label.
Which projects are covered
Symfony’s scope includes projects hosted in five GitHub organizations, including versions that are no longer maintained:
- symfony, covering Symfony, its components and bundles, Symfony UX and Symfony AI, among other projects;
- symfony-cli, for the Symfony CLI;
- symfony-tools, for tools used to build Symfony;
- twigphp, for Twig and its extensions;
- symfonycorp, for projects from Symfony SAS.
That boundary matters for products assembled from multiple packages. Symfony will assign identifiers for vulnerabilities in the projects within those organizations, but it won’t handle vulnerabilities in their dependencies. Those issues remain with the dependency maintainers or the CNA responsible for that software. Users therefore still need to follow upstream advisories for third party components, even when they consume them as part of a Symfony application.
What users will see
The existing advisory channels stay in place. For each fixed vulnerability, users will continue to see a GitHub security advisory, a post in Symfony’s Security Advisories blog category, and a listing in the FriendsOfPHP security advisories database.
The added CVE Record will include affected versions, a CVSS score and credits, and should appear within a day of the advisory. Symfony also says that a URL in the form https://symfony.com/cve-YYYY-NNNNN will lead to the matching blog post for each CVE ID it assigns. This gives teams a direct route from the identifier to Symfony’s own description of the issue.
Anyone who discovers a vulnerability in a covered project can continue reporting it to security [at] symfony.com. Symfony says the same address can be used to request a CVE ID for a vulnerability that is already public. Its CNA policy explains how the organization assigns IDs and how to dispute a decision.
What to watch
The main change is operational rather than a change to how users receive fixes: Symfony is taking responsibility for numbering vulnerabilities in its own project scope, with a stated schedule for publishing identifiers and records. Teams that already track GitHub advisories, Symfony’s blog and FriendsOfPHP can keep using those channels while adding CVE Records to their workflows.
The scope boundary is the detail to keep in mind. A vulnerability in a Symfony component and one in a library it depends on may have different maintainers and different CVE assignment paths. For maintainers, security teams and package consumers, the useful test will be whether the promised publication cadence holds as advisories arrive, and whether the record’s affected-version details are clear enough to support triage across maintained and older releases.
Symfony thanked Red Hat’s Root CNA team for guiding its onboarding and Checkmarx, including Bruno Dias and his team, for helping assign IDs before the change. The shift should make Symfony’s own advisories easier to reference promptly; dependency coverage will still depend on the teams responsible for those packages.