CVE-2026-133276: pydantic · Improper Input Validation
Affects pydanticSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.10.27 when convenient.
Data as of 19 Nov 2026, 16:41 UTC
Thin evidence
One scorer or none| CNA (Pydantic) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 1.10.27
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade pydantic to 1.10.27.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pydanticpydantic | Affected
| Fixed in
|
PyPIpydanticpkg:pypi/pydanticOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade affected Pydantic V1 versions to 1.10.27 or later to apply the official fix. For users of Pydantic V2 relying on the pydantic.v1 namespace, upgrading to version 2.14.2 or later is recommended. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-133276 is a vulnerability in Pydantic V1 dataclasses that allows improper input validation when extra data is permitted (extra=Extra.allow). By providing a special key __pydantic_initialised__, an attacker can bypass validation, causing field values to be accepted without proper checks. This leads to data returned by validation not matching the declared types. The flaw affects Pydantic versions from 1.10.0 up to but not including 1.10.27. It was fixed in version 1.10.27, and users of Pydantic V2 relying on the pydantic.v1 namespace should upgrade to 2.14.2 or later.
References
- github.com/pydantic/pydantic/security/advisories/GHSA-r49w-vh47-r4hf (opens in a new tab)
- github.com/pydantic/pydantic/blob/v1.10.26/pydantic/dataclasses.py (opens in a new tab)
- github.com/pydantic/pydantic/blob/v1.10.26/pydantic/dataclasses.py (opens in a new tab)
- github.com/pydantic/pydantic/commit/b26913fe6 (opens in a new tab)
- github.com/pydantic/pydantic/releases/tag/v2.14.2 (opens in a new tab)