CVE-2026-133276
When extra data is allowed (extra=Extra.allow), providing a …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/pydantic/pydantic/blob/v1.10.26/pydantic/dataclasses.py#L295-L298
- github.com/pydantic/pydantic/blob/v1.10.26/pydantic/dataclasses.py#L430-L434
- github.com/pydantic/pydantic/commit/b26913fe6
- github.com/pydantic/pydantic/releases/tag/v2.14.2
- github.com/pydantic/pydantic/security/advisories/GHSA-r49w-vh47-r4hf
- nvd.nist.gov/vuln/detail/CVE-2026-133276
- cve.org/CVERecord?id=CVE-2026-133276
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.