{"slug": "pydantic-is-now-a-cve-numbering-authority", "title": "Pydantic is now a CVE Numbering Authority", "summary": "The CVE Program added Pydantic as a CVE Numbering Authority (CNA) on November 17, letting Pydantic assign CVE IDs and publish CVE records for vulnerabilities in the open-source projects it maintains, including Pydantic, Pydantic AI, Pydantic Monty, and httpx2. Pydantic said assigning its own IDs removes its share of the GitHub CNA review queue and lets records ship with the fixed release instead of days later, with each record listing affected and fixed versions, impact, mitigations, and reporter credit. Reporting channels are unchanged: GitHub's Security tab \"Report a vulnerability\" or security@pydantic.dev.", "body_md": "On November 17, the CVE Program [added Pydantic as a CVE Numbering Authority (CNA)](https://www.cve.org/Media/News/item/news/2026/11/17/Pydantic-Added-as-CNA).\nWe can now assign CVE IDs and publish CVE records for vulnerabilities in the open-source projects we maintain, including\nPydantic, [Pydantic AI](https://pydantic.dev/pydantic-ai), Pydantic Monty, and httpx2.\n\n## \n\nThe number of [security reports to our projects](https://pydantic.dev/articles/hack-monty-postmortem) has grown a lot this year. Each valid one ends the same way: a fix, a\nrelease, and an advisory telling you whether you are affected.\n\nThe CVE ID is the name the rest of the industry uses for that vulnerability. Scanners such as `pip-audit` and\nDependabot read databases that also carry GHSA and PYSEC IDs, but the CVE is the alias that ties those records together,\nand it is the ID your security team will ask about.\n\nUntil now, every ID came from GitHub, which acts as the CNA for advisories published through its Security tab. GitHub reviews each request, and it does so for the whole open-source ecosystem, where report volume has grown just as fast as ours. Assigning our own IDs takes our share off that queue and removes the one step between a fix and its CVE that we did not control.\n\n## \n\nWe assign the CVE ID ourselves, so the record can go out with the fixed release instead of days after it. Each record lists the affected and fixed versions, the impact, any mitigations, and credit for the reporter when they want it.\n\n## \n\nNothing changes in how you report. Use the affected project's private reporting channel: on GitHub, open the\n**Security** tab and choose **Report a vulnerability**. If a project has no private channel, email\n[security@pydantic.dev](mailto:security@pydantic.dev). Please do not open a public issue.\n\nOur scope, disclosure policy, and published advisories live at [security.pydantic.dev](https://security.pydantic.dev/).\n\nThanks to the [Red Hat Root](https://www.cve.org/PartnerInformation/ListofPartners/partner/redhat) and the CVE Program\nfor bringing us on board, and to everyone who has reported an issue to us privately. Keep them coming.", "url": "https://wpnews.pro/news/pydantic-is-now-a-cve-numbering-authority", "canonical_source": "https://pydantic.dev/articles/pydantic-cve-numbering-authority", "published_at": "2026-11-19 09:00:00+00:00", "updated_at": "2026-11-20 14:44:20.465527+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "ai-agents"], "entities": ["Pydantic", "CVE Program", "Pydantic AI", "Pydantic Monty", "httpx2", "GitHub", "Red Hat Root", "pip-audit"], "also_reported_by": [], "takeaway": null, "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/pydantic-is-now-a-cve-numbering-authority", "markdown": "https://wpnews.pro/news/pydantic-is-now-a-cve-numbering-authority.md", "text": "https://wpnews.pro/news/pydantic-is-now-a-cve-numbering-authority.txt", "jsonld": "https://wpnews.pro/news/pydantic-is-now-a-cve-numbering-authority.jsonld"}}