Pydantic Becomes CVE Numbering Authority to Accelerate Security Disclosures
Pydantic is now a CVE Numbering Authority, enabling it to assign its own vulnerability IDs and publish security records simultaneously with software fixes.
On November 17, the CVE Program officially added Pydantic as a CVE Numbering Authority (CNA). This designation allows the organization to independently assign Common Vulnerabilities and Exposures (CVE) identifiers and publish official security records for vulnerabilities found in the open-source projects it maintains. The scope of this authority includes core libraries such as Pydantic, Pydantic AI, Pydantic Monty, and httpx2.
The move addresses a growing bottleneck in the open-source security ecosystem. As the volume of valid security reports has increased significantly this year, the traditional workflow required every new vulnerability ID to be issued by GitHub, which acts as the CNA for advisories published through its Security tab. GitHub reviews these requests for the entire open-source community, leading to delays between a fix being released and its corresponding CVE record becoming public. By assuming the role of CNA, Pydantic removes this dependency on an external queue.
For developers and security teams, the practical impact is speed and clarity. Previously, a fixed release might appear days before the associated CVE ID was assigned, creating a gap where scanners like pip-audit or Dependabot could not immediately correlate the patch with a standardized identifier. Now, Pydantic can publish the CVE record at the exact moment the fixed version is released. Each record will detail affected and fixed versions, the nature of the impact, available mitigations, and credit for reporters who wish to be acknowledged.
The reporting process for users remains unchanged. Vulnerabilities should still be disclosed privately via the affected project's GitHub Security tab or by emailing security@pydantic.dev if no private channel exists. Public issue trackers are explicitly discouraged for initial disclosure. The Red Hat Root and the broader CVE Program facilitated this partnership, acknowledging the need for distributed authority in high-volume maintenance environments.