# GHSA-GJ4F-R7MF-JJXH: Unbounded exponent in Fraction validation

- Database: GitHub
- Severity: CVSS 6.3 (Medium)
- Published: 2026-10-29
- Modified: 2026-11-19

## Tracked as

- [CVE-2026-133426](https://cve.now/CVE-2026-133426.md): Pydantic denial of service in Fraction exponent validation

## Affected versions

- pydantic (PyPI): from 2.10.0, fixed in 2.14.0

## Description

### Summary

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.

### Details

String inputs are passed to the [`Fraction`](https://docs.python.org/3/library/fractions.html#fractions.Fraction) constructor. For strings in exponent notation (e.g. `'1e8000000'`), CPython computes the corresponding power of ten as an integer ([`Lib/fractions.py`](https://github.com/python/cpython/blob/v3.14.8/Lib/fractions.py#L275-L281)):

```python
exp = m.group('exp')
if exp:
    exp = int(exp)
    if exp >= 0:
        numerator *= 10**exp
    else:
        denominator *= 10**-exp
```

The issue was fixed in commit https://github.com/pydantic/pydantic/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.

## References

- https://github.com/pydantic/pydantic/security/advisories/GHSA-gj4f-r7mf-jjxh

Page: https://cve.now/GHSA-GJ4F-R7MF-JJXH
