Skip to main content
Menu
CVEs

Pydantic denial of service in multi-host URL validation

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

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

Summary

Pydantic is affected by a bug where validating an untrusted URL with a long scheme and many hosts into a multi-host URL field, such as PostgresDsn, takes quadratic time and memory. A remote attacker who can send such input without logging in can use it to cause denial of service, since a roughly 100-kilobyte string can consume around a gigabyte of memory during validation.

Written by a model

Original description

Validating an untrusted URL with a long scheme and many hosts into a multi-host URL field (e.g. PostgresDsn) takes quadratic time and memory: an input of about a hundred kilobytes takes around a gigabyte of memory to validate.

The parse_multihost_url() function (in pydantic-core/src/validators/url.rs) parses each host separately, prepending the whole URL prefix (including the scheme) to every one of them. As the scheme can be arbitrarily long, and is parsed and stored once per host, both time and memory grow quadratically with the input size. Allowed schemes (e.g. postgres for PostgresDsn) are only checked after parsing, so they don't prevent the issue.

The issue was fixed in commit b4028f9d87e34750e53be0ba011d70f3c0fcc94e.

Impact: denial of service through validation of untrusted input. Affected are applications validating untrusted strings into multi-host URL fields (PostgresDsn, MongoDsn, NatsDsn, or custom types built on MultiHostUrl).

What to do

Upgrade to a fixed version: 2.14.0.

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-133428 (Quadratic time and memory multi-host URL validation), 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-133428 (entry last updated 2026-11-20):
Affected:
- PyPI package pydantic: from 2.0.0, fixed in 2.14.0
Fixed versions: 2.14.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133428 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133428 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-955g-x97g-8mcp
- https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/url.rs#L537
- https://github.com/pydantic/pydantic/blob/v2.13.5/pydantic-core/src/validators/url.rs#L644-L649
- https://github.com/pydantic/pydantic/commit/b4028f9d87e34750e53be0ba011d70f3c0fcc94e
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-133428
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-133428"}.

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

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

pydantic (PyPI): from 2.0.0 before 2.14.0.

Source: cve.now feed data

How do I fix CVE-2026-133428?

Upgrade to a fixed version: 2.14.0.

Source: cve.now feed data

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