CVE-2026-133424
What it is
When extra data is allowed, providing both the alias and the name of an aliased TypedDict or dataclass field makes the unvalidated value (provided under the name) overwrite the validated one (provided under the alias), resulting in validated data not matching the declared type. Extra items are stored in the same dictionary as the fields (the returned dictionary for TypedDict, the instance __dict__ for dataclasses). As only the alias is marked as used, the field name is treated as an extra item, and its unvalidated value overrides the validated one. The TypedDict validator (pydantic-core/src/validators/typed_dict.rs) and the dataclass validator (pydantic-core/src/validators/dataclass.rs) share this logic. The issue was fixed in commit 34491f5328f168f14e3769cd5f0f83c0af0f4778. Impact: validation bypass, as data returned by validation doesn't match the declared type. Affected are applications validating untrusted data into TypedDict or dataclass types with aliased fields and extra data allowed (with extra='allow', or with the extra_items argument for TypedDict), using Pydantic V2 (up to and including 2.14.1). Pydantic models (BaseModel) are not affected, as extra data is stored separately from fields.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: 6.3 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Weakness
- CWE-20 · Improper input validation
- Record status
- Received
Affected
- Pydantic < 2.14.2
Attack profile CVSS 4.0 · 6.3
- Attack vector
- Network
- Complexity
- Low
- Attack requirements
- Present
- Privileges needed
- None
- User interaction
- None
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-133424.md and follow it. Check whether this project is affected by CVE-2026-133424. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/pydantic/pydantic/security/advisories/GHSA-3r8g-cqwr-jr29
- https://github.com/pydantic/pydantic/commit/34491f5328f168f14e3769cd5f0f83c0af0f4778
References
- https://github.com/pydantic/pydantic/security/advisories/GHSA-3r8g-cqwr-jr29
- https://github.com/pydantic/pydantic/blob/becee9cc0ef8132e854762448fde76aa56608c6b/pydantic-core/src/validators/dataclass.rs#L215-L342
- https://github.com/pydantic/pydantic/blob/becee9cc0ef8132e854762448fde76aa56608c6b/pydantic-core/src/validators/typed_dict.rs#L204-L225
- https://github.com/pydantic/pydantic/commit/34491f5328f168f14e3769cd5f0f83c0af0f4778