PT-2026-151847
CVE-2026-133276
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
CVSS 4.0
6.3
MediumMetricsAV: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
Name of the Vulnerable Software and Affected Versions
Pydantic versions prior to 1.10.27
Pydantic versions prior to 2.14.2
Description
When a Pydantic V1 dataclass is configured to allow extra data via
extra=Extra.allow, providing a pydantic initialised key during validation causes the system to treat the object as already validated. This occurs because the init () method stores all keyword arguments in the instance dict before validation, allowing the pydantic initialised argument to override the internal flag used to skip validation. Consequently, field values are not validated, and the returned data may not match the declared types. This issue affects applications that validate untrusted data using Pydantic V1 dataclasses with extra data enabled.Recommendations
Update to version 1.10.27 or later.
Update to version 2.14.2 or later for users relying on the
pydantic.v1 namespace.Exploitability
Exploit
Fix
Impacts
Vendors
Affected products
Found an issue in the description? Have something to add? Feel free to write us 👾