When extra data is allowed (extra=Extra.allow), providing a pydantic_initialised key when validating a Pydantic V1 dataclass makes it considered as already validated, resulting in field values not being validated. The init() method of Pydantic V1 dataclasses stores all the provided keyword arguments in the instance dict before validation, so a pydantic_initialised keyword argument overrides the internal flag used to skip validation of already validated instances. As a result, data returned by validation doesn't match the declared type. Affected are applications validating untrusted data into Pydantic V1 dataclasses allowing extra data. The issue was fixed in Pydantic 1.10.27. Users relying on the pydantic.v1 namespace in Pydantic V2 should upgrade to 2.14.2 or later.
{
"cna_assigner": "Pydantic",
"cwe_ids": [
"CWE-20"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/133xxx/CVE-2026-133276.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "1.10.0"
},
{
"fixed": "1.10.27"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "b26913fe6"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v2.14.2",
"range": [
{
"fixed": "aa540acc29960fb394312cf97d888c99f9686814"
}
],
"source": "REFERENCES_TAG"
}
]
}