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.
{
"cna_assigner": "Pydantic",
"cwe_ids": [
"CWE-20"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/133xxx/CVE-2026-133429.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "2.13.0"
},
{
"fixed": "2.14.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "4c65dbda9970a488e2ff21c8693fc6f6d70a3358"
}
],
"source": "REFERENCES_COMMIT"
}
]
}