Skip to main content
Menu
CVEs

Pydantic validation bypass in dataclasses accepting extra data

CVE-2026-133276Published November 19, 2026, updated

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

Summary

Pydantic is affected: when extra data is allowed, a crafted `__pydantic_initialised__` keyword can be passed to a Pydantic V1 dataclass and make it skip field validation. An attacker can reach this remotely, without logging in, by sending such input to an application that validates untrusted data into these dataclasses, so the returned data may not match the declared types.

Written by a model

Original description

When 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.

What to do

Upgrade to a fixed version: 1.10.27.

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-133276 (Validation bypass of Pydantic V1 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-133276 (entry last updated 2026-11-19):
Affected:
- PyPI package pydantic: from 1.10.0, fixed in 1.10.27
Fixed versions: 1.10.27.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133276 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133276 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-r49w-vh47-r4hf
- https://github.com/pydantic/pydantic/blob/v1.10.26/pydantic/dataclasses.py#L295-L298
- https://github.com/pydantic/pydantic/blob/v1.10.26/pydantic/dataclasses.py#L430-L434
- https://github.com/pydantic/pydantic/commit/b26913fe6
- https://github.com/pydantic/pydantic/releases/tag/v2.14.2
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-133276
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-133276"}.

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 7

Questions about CVE-2026-133276

Is CVE-2026-133276 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-133276?

pydantic (PyPI): from 1.10.0 before 1.10.27.

Source: cve.now feed data

How do I fix CVE-2026-133276?

Upgrade to a fixed version: 1.10.27.

Source: cve.now feed data

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