cd /news/ai-tools/pydantic-is-now-a-cve-numbering-auth… · home › topics › ai-tools › article
[ARTICLE · art-173283] src=pydantic.dev ↗ pub= topic=ai-tools verified=true sentiment=↑ positive

Pydantic is now a CVE Numbering Authority

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.

by read2 min views1 publishedNov 19, 2026
Pydantic is now a CVE Numbering Authority
Image: Pydantic (auto-discovered)

On November 17, the CVE Program added Pydantic as a CVE Numbering Authority (CNA). We can now assign CVE IDs and publish CVE records for vulnerabilities in the open-source projects we maintain, including

Pydantic, Pydantic AI, Pydantic Monty, and httpx2.

#

The number of security reports to our projects has grown a lot this year. Each valid one ends the same way: a fix, a release, and an advisory telling you whether you are affected.

The CVE ID is the name the rest of the industry uses for that vulnerability. Scanners such as pip-audit and Dependabot read databases that also carry GHSA and PYSEC IDs, but the CVE is the alias that ties those records together, and it is the ID your security team will ask about.

Until 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.

#

We 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.

#

Nothing changes in how you report. Use the affected project's private reporting channel: on GitHub, open the Security tab and choose Report a vulnerability. If a project has no private channel, email

security@pydantic.dev. Please do not open a public issue. Our scope, disclosure policy, and published advisories live at security.pydantic.dev.

Thanks to the Red Hat Root and the CVE Program for bringing us on board, and to everyone who has reported an issue to us privately. Keep them coming.

── more in #ai-tools 4 stories · sorted by recency
── more on @pydantic 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/pydantic-is-now-a-cv…] indexed:0 read:2min 2026-11-19 · —