Skip to main content
Menu
CVEs

Pydantic denial of service in Fraction exponent validation

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

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

Summary

Pydantic's validation of untrusted strings in exponent notation for Fraction fields computes an unbounded power of ten, which can cause denial of service. A remote attacker can trigger it without logging in by sending a string of only a few bytes, which takes seconds to validate.

Written by a model

Original description

Validating an untrusted string in exponent notation into a Fraction field computes the full power of ten without any bound: an input of a few bytes takes seconds to validate.

String inputs are passed to the Fraction constructor. For strings in exponent notation (e.g. '1e8000000'), CPython computes the corresponding power of ten as an integer (in Lib/fractions.py).

The issue was fixed in commit 69ed168e9ad465eef4c8d81efb152a93b604daf5. For strings in exponent notation, the exponent is now parsed before calling the Fraction constructor, and exponents larger than 4300 (in absolute value) are rejected.

Impact: denial of service through validation of untrusted input. Affected are applications validating untrusted strings into Fraction fields (in both JSON and Python mode, including in strict mode), using Pydantic from 2.10.0 up to (but excluding) 2.14.0.

From 2.14.0, exponents larger than 4300 (in absolute value) are rejected, matching the maximum number of digits accepted for integers.

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-133426 (Unbounded exponent in Fraction 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-133426 (entry last updated 2026-11-20):
Affected:
- PyPI package pydantic: from 2.10.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-133426 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133426 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-gj4f-r7mf-jjxh
- https://github.com/python/cpython/blob/v3.14.8/Lib/fractions.py#L275-L281
- https://github.com/pydantic/pydantic/commit/69ed168e9ad465eef4c8d81efb152a93b604daf5
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-133426
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-133426"}.

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 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · pydantic/pydantic · Advisory GHSA-gj4f-r7mf-jjxh
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133426
RecordNVD · CVE-2026-133426
Other links 2
RepositoryGitHub · python/cpython · Lib/fractions.py · L275-L281
RepositoryGitHub · pydantic/pydantic · Commit 69ed168e

Questions about CVE-2026-133426

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

pydantic (PyPI): from 2.10.0 before 2.14.0.

Source: cve.now feed data

How do I fix CVE-2026-133426?

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.