<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/symfony-is-now-a-cve-numbering-authority-symfony-blog--lbmk5ntqe" -->

---
title: Symfony is now a CVE Numbering Authority (Symfony Blog)
description: Symfony is now a CVE Numbering Authority, with Red Hat acting as its Root CNA. The project can now assign CVE IDs to its own vulnerabilities and publish CVE...
canonical: https://daily.dev/posts/symfony-is-now-a-cve-numbering-authority-symfony-blog--lbmk5ntqe
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Symfony is now a CVE Numbering Authority (Symfony Blog) | daily.dev
og:description: Symfony is now a CVE Numbering Authority, with Red Hat acting as its Root CNA. The project can now assign CVE IDs to its own vulnerabilities and publish CVE...
og:url: https://daily.dev/posts/symfony-is-now-a-cve-numbering-authority-symfony-blog--lbmk5ntqe
og:image: https://api.daily.dev/og/posts/lBMk5ntqe.png
og:image:alt: Symfony is now a CVE Numbering Authority (Symfony Blog)
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Symfony is now a CVE Numbering Authority (Symfony Blog)

**[Symfony](https://daily.dev/sources/symfony)** · 2 min read · 0 upvotes · 0 comments

## Summary

Symfony is now a CVE Numbering Authority, with Red Hat acting as its Root CNA. The project can now assign CVE IDs to its own vulnerabilities and publish CVE Records directly. Every advisory will now get a CVE ID the day it's published, with the full CVE Record following within a day. The scope covers Symfony, Symfony UX, Symfony AI, the Symfony CLI, Symfony's build tools, Twig and its extensions, and Symfony SAS projects, but not their dependencies. Each CVE ID links to a blog post at symfony.com/cve-YYYY-NNNNN, and the CVE Record includes affected versions, CVSS score, and credits.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://symfony.com/blog/symfony-is-now-a-cve-numbering-authority>

## Questions this post answers

### What changes now that Symfony is a CVE Numbering Authority?

Symfony assigns CVE IDs to its own vulnerabilities and publishes CVE Records directly, under Red Hat as its Root CNA. Previously it requested CVE IDs from GitHub, which sometimes took weeks; Checkmarx also stepped in to help in recent months. Now every advisory gets a CVE ID the day it's published, with the full CVE Record following within a day.

_Developers tracking Symfony security fixes can follow CVE advisories as they're published through daily.dev._

### Which projects are covered by Symfony's CVE Numbering Authority scope?

The scope covers projects hosted under the symfony, symfony-cli, symfony-tools, twigphp, and symfonycorp GitHub organizations, including Symfony, its components and bundles, Symfony UX, Symfony AI, the Symfony CLI, Twig and its extensions, and Symfony SAS projects. Dependencies of these projects are excluded; their CVE IDs come from their own maintainers or CNA.

_Teams auditing their PHP dependency tree can keep tabs on scope changes like this via daily.dev._

### Where can I find the CVE Record for a specific Symfony vulnerability?

Each CVE ID assigned by Symfony links to a matching blog post at the URL pattern https://symfony.com/cve-YYYY-NNNNN, which includes the affected versions, CVSS score, and credits. Advisories still also appear as GitHub security advisories, posts in the Security Advisories blog category, and entries in the FriendsOfPHP security advisories database.

_Developers who need quick access to CVSS scores and affected versions can track these advisories on daily.dev._

## Similar posts on daily.dev

- [Symfony 5.4.54 released \(Symfony Blog\)](https://daily.dev/posts/symfony-5-4-54-released-symfony-blog--fsrfny00g) · Symfony · 1 upvotes · 0 comments
- [Claude Mythos Audited Symfony and Found 19 Vulnerabilities \(Symfony Blog\)](https://daily.dev/posts/claude-mythos-audited-symfony-and-found-19-vulnerabilities-symfony-blog--uhd6sjyip) · Symfony · 4 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#php](https://daily.dev/tags/php), [#symfony](https://daily.dev/tags/symfony)

[View this post on daily.dev](https://daily.dev/posts/symfony-is-now-a-cve-numbering-authority-symfony-blog--lbmk5ntqe)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Symfony is now a CVE Numbering Authority (Symfony Blog)","url":"https://daily.dev/posts/symfony-is-now-a-cve-numbering-authority-symfony-blog--lbmk5ntqe","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/symfony-is-now-a-cve-numbering-authority-symfony-blog--lbmk5ntqe"},"datePublished":"2026-11-18T03:42:48.279Z","dateModified":"2026-11-18T04:06:21.863Z","description":"Symfony is now a CVE Numbering Authority, with Red Hat acting as its Root CNA. The project can now assign CVE IDs to its own vulnerabilities and publish CVE...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/327b244859fddae8f3a20d0225898aa0?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/327b244859fddae8f3a20d0225898aa0?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Symfony","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Symfony","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/cc07051b7112472f9729e73c14660a64","url":"https://daily.dev/sources/symfony"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/symfony-is-now-a-cve-numbering-authority-symfony-blog--lbmk5ntqe","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,php,symfony","timeRequired":"PT2M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Symfony","item":"https://daily.dev/sources/symfony"},{"@type":"ListItem","position":3,"name":"Symfony is now a CVE Numbering Authority (Symfony Blog)"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/symfony-is-now-a-cve-numbering-authority-symfony-blog--lbmk5ntqe#faq","mainEntity":[{"@type":"Question","name":"What changes now that Symfony is a CVE Numbering Authority?","acceptedAnswer":{"@type":"Answer","text":"Symfony assigns CVE IDs to its own vulnerabilities and publishes CVE Records directly, under Red Hat as its Root CNA. Previously it requested CVE IDs from GitHub, which sometimes took weeks; Checkmarx also stepped in to help in recent months. Now every advisory gets a CVE ID the day it's published, with the full CVE Record following within a day. Developers tracking Symfony security fixes can follow CVE advisories as they're published through daily.dev."}},{"@type":"Question","name":"Which projects are covered by Symfony's CVE Numbering Authority scope?","acceptedAnswer":{"@type":"Answer","text":"The scope covers projects hosted under the symfony, symfony-cli, symfony-tools, twigphp, and symfonycorp GitHub organizations, including Symfony, its components and bundles, Symfony UX, Symfony AI, the Symfony CLI, Twig and its extensions, and Symfony SAS projects. Dependencies of these projects are excluded; their CVE IDs come from their own maintainers or CNA. Teams auditing their PHP dependency tree can keep tabs on scope changes like this via daily.dev."}},{"@type":"Question","name":"Where can I find the CVE Record for a specific Symfony vulnerability?","acceptedAnswer":{"@type":"Answer","text":"Each CVE ID assigned by Symfony links to a matching blog post at the URL pattern https://symfony.com/cve-YYYY-NNNNN, which includes the affected versions, CVSS score, and credits. Advisories still also appear as GitHub security advisories, posts in the Security Advisories blog category, and entries in the FriendsOfPHP security advisories database. Developers who need quick access to CVSS scores and affected versions can track these advisories on daily.dev."}}]}
```

