CVE-2026-133426: Unbounded exponent in Fraction validation
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.14.0
Event History
Frequently Asked Questions
Which deployments are exposed?
Applications using Pydantic versions 2.10.0 through versions before 2.14.0 are affected if they validate untrusted strings into Fraction fields. This applies to both JSON and Python validation modes, including strict mode.
What does an attacker need to trigger the issue?
An attacker only needs to provide an untrusted string in exponent notation to a Fraction field, such as "1e8000000". A short input can cause expensive computation of a very large power of ten during validation, resulting in denial of service.
Are default validation protections or strict mode sufficient to prevent exploitation?
No. The issue affects Fraction string validation in both JSON and Python mode, including strict mode.
What version resolves the issue, and what changes after upgrading?
Pydantic 2.14.0 resolves the issue by parsing exponents before constructing the Fraction and rejecting exponent values whose absolute value exceeds 4300.