CVE-2026-133426

Description

A flaw was found in pydantic. When validating untrusted input formatted in scientific exponent notation into Fraction fields, the library calculates large powers of ten without restriction. A remote attacker can exploit this issue by submitting specially crafted numeric strings, causing excessive CPU consumption and resulting in a Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate impact because successful exploitation results in excessive CPU consumption and denial of service, without impacting data confidentiality or integrity. Exploitation requires an application to deserialize user-supplied input into schemas explicitly configured with Fraction data types. In typical Red Hat deployments, applications rarely expose unauthenticated endpoints parsing Fraction fields, substantially limiting the real-world attack surface across supported environments.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.3N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactLowN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)

When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.

Frequently Asked Questions

Want to get errata notifications? Sign up here.