PT-2026-152732
CVE-2026-133429
·
Published
2026-11-20
·
Updated
2026-11-20
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
When validating JSON data into a model allowing extra data, the keys of extra data aren't validated against the key type annotated on pydantic extra , resulting in extra data not matching the declared type. This is the case if you define pydantic extra as e.g. dict[Annotated[str, Field(pattern=r'^x ')], int].
The validate json by iteration() method (in pydantic-core/src/validators/model fields.rs), used to validate JSON data into models, only validates the values of extra data, and stores the keys as is.
The issue was fixed in commit 4c65dbda9970a488e2ff21c8693fc6f6d70a3358.
Impact: validation bypass, as extra data returned by validation doesn't match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with extra='allow'), with a key type annotated on pydantic extra (e.g. dict[Annotated[str, Field(pattern=...)], int]), using Pydantic from 2.13.0 up to (but excluding) 2.14.2.
Python mode validation isn't affected.
Found an issue in the description? Have something to add? Feel free to write us 👾