Skip to main content
Menu
CVEs

Pydantic validation bypass in TypedDict and dataclass aliases

CVE-2026-133424Published November 20, 2026, updated

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.14.2
Who is exposed
Not reported

Summary

Pydantic (the pydantic package) has a validation bypass affecting TypedDict and dataclass types with aliased fields when extra data is allowed. A remote attacker who can send untrusted input without logging in can supply both an alias and the field name, so the unvalidated value overwrites the validated one and the returned data no longer matches the declared type.

Written by a model

Original description

When extra data is allowed, providing both the alias and the name of an aliased TypedDict or dataclass field makes the unvalidated value (provided under the name) overwrite the validated one (provided under the alias), resulting in validated data not matching the declared type.

Extra items are stored in the same dictionary as the fields (the returned dictionary for TypedDict, the instance __dict__ for dataclasses). As only the alias is marked as used, the field name is treated as an extra item, and its unvalidated value overrides the validated one. The TypedDict validator (pydantic-core/src/validators/typed_dict.rs) and the dataclass validator (pydantic-core/src/validators/dataclass.rs) share this logic.

The issue was fixed in commit 34491f5328f168f14e3769cd5f0f83c0af0f4778.

Impact: validation bypass, as data returned by validation doesn't match the declared type. Affected are applications validating untrusted data into TypedDict or dataclass types with aliased fields and extra data allowed (with extra='allow', or with the extra_items argument for TypedDict), using Pydantic V2 (up to and including 2.14.1).

Pydantic models (BaseModel) are not affected, as extra data is stored separately from fields.

What to do

Upgrade to a fixed version: 2.14.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133424 (Validation bypass of aliased fields in TypedDict and dataclasses allowing extra data), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133424 (entry last updated 2026-11-20):
Affected:
- PyPI package pydantic: from 2.0, fixed in 2.14.2
Fixed versions: 2.14.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133424 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133424 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/pydantic/pydantic/security/advisories/GHSA-3r8g-cqwr-jr29
- https://github.com/pydantic/pydantic/blob/becee9cc0ef8132e854762448fde76aa56608c6b/pydantic-core/src/validators/typed_dict.rs#L204-L225
- https://github.com/pydantic/pydantic/blob/becee9cc0ef8132e854762448fde76aa56608c6b/pydantic-core/src/validators/dataclass.rs#L215-L342
- https://github.com/pydantic/pydantic/commit/34491f5328f168f14e3769cd5f0f83c0af0f4778
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133424
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133424"}.

Affected versions

cve.now Index

43Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach20/20pydantic: 275.4M downloads a week
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 88 if added to CISA KEV
  • Would score about 83 if CISA's SSVC rates exploitation active
  • Would score about 48 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 6

Questions about CVE-2026-133424

Is CVE-2026-133424 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133424?

pydantic (PyPI): from 2.0 before 2.14.2.

Source: cve.now feed data

How do I fix CVE-2026-133424?

Upgrade to a fixed version: 2.14.2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.