CVE-2026-133276

NameCVE-2026-133276
DescriptionWhen 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.
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
pydantic (PTS)bookworm1.10.4-1+deb12u1vulnerable
trixie2.10.6-2fixed
forky, sid2.14.1-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
pydanticsource(unstable)2.4.2-1

Notes

[bookworm] - pydantic <postponed> (Minor issue, validation bypass when extra=Extra.allow)
https://github.com/pydantic/pydantic/security/advisories/GHSA-r49w-vh47-r4hf
Fixed by: https://github.com/pydantic/pydantic/commit/b26913fe6bbdefb6a75b00f6cb64fc7c059aba48 (v1.10.27)
Upstream notes that if relying on the pydantic.v1 namespace in Pydantic V2 an
upgrade to v2.14.2. The fix is specific for 1.10.x branch. Mark first version
in 2.x series as the fixed version.

Search for package or bug name: Reporting problems