CVE-2026-133429 (GCVE-0-2026-133429)
Vulnerability from cvelistv5 – Published: 2026-11-20 07:32 – Updated: 2026-11-20 17:18
VLAI
EPSS
VEX
Title
Validation bypass of extra data keys in JSON model validation
Summary
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.
Severity
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-20 17:18 UTC
CWE
- CWE-20 - Improper Input Validation
References
Impacted products
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133429",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T17:18:36.430640Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T17:18:45.072Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://pypi.org",
"defaultStatus": "unaffected",
"packageName": "pydantic",
"product": "pydantic",
"repo": "https://github.com/pydantic/pydantic",
"vendor": "pydantic",
"versions": [
{
"lessThan": "2.14.2",
"status": "affected",
"version": "2.13.0",
"versionType": "python"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "lullu57"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003ch3\u003eSummary\u003c/h3\u003e\n\u003cp\u003eWhen validating JSON data into a model allowing extra data, the keys of extra data aren\u0027t validated against the key type annotated on \u003ccode\u003e__pydantic_extra__\u003c/code\u003e, resulting in extra data not matching the declared type. This is the case if you define \u003ccode\u003e__pydantic_extra__\u003c/code\u003e as e.g. \u003ccode\u003edict[Annotated[str, Field(pattern=r\u0027^x_\u0027)], int]\u003c/code\u003e.\u003c/p\u003e\n\u003ch3\u003eDetails\u003c/h3\u003e\n\u003cp\u003eThe \u003ca href=\"https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L540\"\u003e\u003ccode\u003evalidate_json_by_iteration()\u003c/code\u003e\u003c/a\u003e method (in \u003ccode\u003epydantic-core/src/validators/model_fields.rs\u003c/code\u003e), used to validate JSON data into models, only validates the values of extra data, and stores the keys as is (\u003ca href=\"https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L605-L623\"\u003eL605-L623\u003c/a\u003e):\u003c/p\u003e\n\u003cpre\u003e\u003ccode class=\"language-rust\"\u003eExtraBehavior::Allow =\u0026gt; {\n // the key is stored as is, without being validated:\n let py_key: Bound\u0026lt;\u0027_, PyString\u0026gt; = new_py_string(py, key, state.cache_str());\n if let Some(validator) = \u0026amp;self.extras_validator {\n match validator.validate(py, value, state) {\n Ok(value) =\u0026gt; {\n model_extra_dict.set_item(\u0026amp;py_key, value)?;\n fields_set.add(py_key)?;\n }\n // ...\n }\n }\n // ...\n}\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003ePython mode validation isn\u0027t affected.\u003c/p\u003e\n\u003cp\u003eThe issue was fixed in commit \u003ca href=\"https://github.com/pydantic/pydantic/commit/4c65dbda9970a488e2ff21c8693fc6f6d70a3358\"\u003e4c65dbda9970a488e2ff21c8693fc6f6d70a3358\u003c/a\u003e.\u003c/p\u003e\n\u003ch3\u003eImpact\u003c/h3\u003e\n\u003cp\u003eValidation bypass: extra data returned by validation doesn\u0027t match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with \u003ccode\u003eextra=\u0027allow\u0027\u003c/code\u003e), with a key type annotated on \u003ccode\u003e__pydantic_extra__\u003c/code\u003e (e.g. \u003ccode\u003edict[Annotated[str, Field(pattern=...)], int]\u003c/code\u003e), using Pydantic from 2.13.0 up to (but excluding) 2.14.2.\u003c/p\u003e\n\u003cp\u003ePython mode validation isn\u0027t affected.\u003c/p\u003e"
}
],
"value": "When validating JSON data into a model allowing extra data, the keys of extra data aren\u0027t 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\u0027^x_\u0027)], int].\n\nThe 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.\n\nThe issue was fixed in commit 4c65dbda9970a488e2ff21c8693fc6f6d70a3358.\n\nImpact: validation bypass, as extra data returned by validation doesn\u0027t match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with extra=\u0027allow\u0027), 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.\n\nPython mode validation isn\u0027t affected."
}
],
"metrics": [
{
"cvssV4_0": {
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-20",
"description": "CWE-20: Improper Input Validation",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T07:32:01.421Z",
"orgId": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"shortName": "Pydantic"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://github.com/pydantic/pydantic/security/advisories/GHSA-qpmf-fgh3-ff25"
},
{
"url": "https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L540"
},
{
"url": "https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L605-L623"
},
{
"url": "https://github.com/pydantic/pydantic/commit/4c65dbda9970a488e2ff21c8693fc6f6d70a3358"
}
],
"source": {
"advisory": "GHSA-qpmf-fgh3-ff25",
"discovery": "UNKNOWN"
},
"title": "Validation bypass of extra data keys in JSON model validation"
}
},
"cveMetadata": {
"assignerOrgId": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"assignerShortName": "Pydantic",
"cveId": "CVE-2026-133429",
"datePublished": "2026-11-20T07:32:01.421Z",
"dateReserved": "2026-11-19T19:50:17.136Z",
"dateUpdated": "2026-11-20T17:18:45.072Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-133429",
"date": "2026-11-22",
"epss": "0.00865",
"percentile": "0.59576"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"collectionURL": "https://pypi.org",
"defaultStatus": "unaffected",
"packageName": "pydantic",
"product": "pydantic",
"repo": "https://github.com/pydantic/pydantic",
"vendor": "pydantic",
"versions": [
{
"lessThan": "2.14.2",
"status": "affected",
"version": "2.13.0",
"versionType": "python"
}
]
}
],
"source": "7cec5f2f-3032-4006-8740-31f605ffab5f"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "When validating JSON data into a model allowing extra data, the keys of extra data aren\u0027t 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\u0027^x_\u0027)], int].\n\nThe 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.\n\nThe issue was fixed in commit 4c65dbda9970a488e2ff21c8693fc6f6d70a3358.\n\nImpact: validation bypass, as extra data returned by validation doesn\u0027t match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with extra=\u0027allow\u0027), 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.\n\nPython mode validation isn\u0027t affected."
}
],
"id": "CVE-2026-133429",
"lastModified": "2026-11-20T18:18:48.410",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV: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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-133429",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T17:18:36.430640Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-20T08:18:32.730",
"references": [
{
"source": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"url": "https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L540"
},
{
"source": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"url": "https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L605-L623"
},
{
"source": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"url": "https://github.com/pydantic/pydantic/commit/4c65dbda9970a488e2ff21c8693fc6f6d70a3358"
},
{
"source": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"url": "https://github.com/pydantic/pydantic/security/advisories/GHSA-qpmf-fgh3-ff25"
}
],
"sourceIdentifier": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-20"
}
],
"source": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"type": "Secondary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-11-20T11:29:34+00:00",
"cve": "CVE-2026-133429",
"id": "CVE-2026-133429",
"initial_release_date": "2026-11-20T07:32:01.421000+00:00",
"product_status:known_affected": "133",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "pydantic: pydantic: Input validation bypass via unvalidated extra keys in JSON data",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-133429.json",
"version": "3"
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-133429",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-20T17:18:36.430640Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T17:18:41.041Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://pypi.org",
"defaultStatus": "unaffected",
"packageName": "pydantic",
"product": "pydantic",
"repo": "https://github.com/pydantic/pydantic",
"vendor": "pydantic",
"versions": [
{
"lessThan": "2.14.2",
"status": "affected",
"version": "2.13.0",
"versionType": "python"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "lullu57"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003ch3\u003eSummary\u003c/h3\u003e\n\u003cp\u003eWhen validating JSON data into a model allowing extra data, the keys of extra data aren\u0027t validated against the key type annotated on \u003ccode\u003e__pydantic_extra__\u003c/code\u003e, resulting in extra data not matching the declared type. This is the case if you define \u003ccode\u003e__pydantic_extra__\u003c/code\u003e as e.g. \u003ccode\u003edict[Annotated[str, Field(pattern=r\u0027^x_\u0027)], int]\u003c/code\u003e.\u003c/p\u003e\n\u003ch3\u003eDetails\u003c/h3\u003e\n\u003cp\u003eThe \u003ca href=\"https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L540\"\u003e\u003ccode\u003evalidate_json_by_iteration()\u003c/code\u003e\u003c/a\u003e method (in \u003ccode\u003epydantic-core/src/validators/model_fields.rs\u003c/code\u003e), used to validate JSON data into models, only validates the values of extra data, and stores the keys as is (\u003ca href=\"https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L605-L623\"\u003eL605-L623\u003c/a\u003e):\u003c/p\u003e\n\u003cpre\u003e\u003ccode class=\"language-rust\"\u003eExtraBehavior::Allow =\u0026gt; {\n // the key is stored as is, without being validated:\n let py_key: Bound\u0026lt;\u0027_, PyString\u0026gt; = new_py_string(py, key, state.cache_str());\n if let Some(validator) = \u0026amp;self.extras_validator {\n match validator.validate(py, value, state) {\n Ok(value) =\u0026gt; {\n model_extra_dict.set_item(\u0026amp;py_key, value)?;\n fields_set.add(py_key)?;\n }\n // ...\n }\n }\n // ...\n}\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003ePython mode validation isn\u0027t affected.\u003c/p\u003e\n\u003cp\u003eThe issue was fixed in commit \u003ca href=\"https://github.com/pydantic/pydantic/commit/4c65dbda9970a488e2ff21c8693fc6f6d70a3358\"\u003e4c65dbda9970a488e2ff21c8693fc6f6d70a3358\u003c/a\u003e.\u003c/p\u003e\n\u003ch3\u003eImpact\u003c/h3\u003e\n\u003cp\u003eValidation bypass: extra data returned by validation doesn\u0027t match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with \u003ccode\u003eextra=\u0027allow\u0027\u003c/code\u003e), with a key type annotated on \u003ccode\u003e__pydantic_extra__\u003c/code\u003e (e.g. \u003ccode\u003edict[Annotated[str, Field(pattern=...)], int]\u003c/code\u003e), using Pydantic from 2.13.0 up to (but excluding) 2.14.2.\u003c/p\u003e\n\u003cp\u003ePython mode validation isn\u0027t affected.\u003c/p\u003e"
}
],
"value": "When validating JSON data into a model allowing extra data, the keys of extra data aren\u0027t 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\u0027^x_\u0027)], int].\n\nThe 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.\n\nThe issue was fixed in commit 4c65dbda9970a488e2ff21c8693fc6f6d70a3358.\n\nImpact: validation bypass, as extra data returned by validation doesn\u0027t match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with extra=\u0027allow\u0027), 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.\n\nPython mode validation isn\u0027t affected."
}
],
"metrics": [
{
"cvssV4_0": {
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"version": "4.0"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-20",
"description": "CWE-20: Improper Input Validation",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T07:32:01.421Z",
"orgId": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"shortName": "Pydantic"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://github.com/pydantic/pydantic/security/advisories/GHSA-qpmf-fgh3-ff25"
},
{
"url": "https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L540"
},
{
"url": "https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/model_fields.rs#L605-L623"
},
{
"url": "https://github.com/pydantic/pydantic/commit/4c65dbda9970a488e2ff21c8693fc6f6d70a3358"
}
],
"source": {
"advisory": "GHSA-qpmf-fgh3-ff25",
"discovery": "UNKNOWN"
},
"title": "Validation bypass of extra data keys in JSON model validation"
}
},
"cveMetadata": {
"assignerOrgId": "7cec5f2f-3032-4006-8740-31f605ffab5f",
"assignerShortName": "Pydantic",
"cveId": "CVE-2026-133429",
"datePublished": "2026-11-20T07:32:01.421Z",
"dateReserved": "2026-11-19T19:50:17.136Z",
"dateUpdated": "2026-11-20T17:18:45.072Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…