Pydantic denial of service in unique_items list validation
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
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
Original 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 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-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"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach20/20pydantic: 275.4M downloads a week
- Severity6.9/10CVSS 6.9
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 97 if added to CISA KEV
- Would score about 92 if CISA's SSVC rates exploitation active
- Would score about 57 if advisories confirm default setups are exposed
Impact
- Widely usedpydantic has 275.4m weekly downloads. pypistats.org150.5k packages depend on pydantic. deps.dev
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · pydantic/pydantic · Advisory GHSA-49g6-96jj-f7r9 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133422 |
| Record | NVD · CVE-2026-133422 |
| Other links 3 | |
| Repository | GitHub · pydantic/pydantic · pydantic/types.py · L612-L620 |
| Repository | GitHub · pydantic/pydantic · Commit 6ec75e57 |
| Repository | GitHub · pydantic/pydantic · Release v2.14.2 |
Questions about CVE-2026-133422
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: cve.now feed data
Which versions are affected by CVE-2026-133422?
pydantic (PyPI): from 1.9.0 through 1.10.26.
Source: cve.now feed data
Related
- CVE-2026-133421Quadratic time timedelta validation in Pydantic V1
- CVE-2026-133424Validation bypass of aliased fields in TypedDict and dataclasses allowing extra data
- CVE-2026-133426Unbounded exponent in Fraction validation
- CVE-2026-133428Quadratic time and memory multi-host URL validation
- CVE-2026-133429Validation bypass of extra data keys in JSON model validation
- CVE-2026-133276Validation bypass of Pydantic V1 dataclasses allowing extra data
No corrections so far. Something wrong on this page? Report an error.