Bug 2577865 (CVE-2026-133424)

Summary: CVE-2026-133424 pydantic: pydantic: Validation bypass via aliased fields
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: alinfoot, anpicker, ansingla, aprice, bbrownin, blitton, brasmith, cahl, cmyers, cochase, dfreiber, dkeler, dnakabaa, dranck, drow, dtrifiro, dymurray, eborisov, ebourniv, ehelms, gbenhaim, gtanzill, hasun, ilpinto, jburrell, jbuscemi, jfula, jlanda, jmitchel, jowilson, jpasqual, jsamir, juwatts, kaycoth, kgaikwad, kshier, lball, lblicha, lcouzens, ljawale, ltomasbo, mhayden, mhulan, msilmser, mwoodson, ngough, niyer, nyancey, oezr, ogajduse, ometelka, osousa, prwatson, ptisnovs, rbobbitt, rchan, rhel-process-autobot, sbunciak, sdoran, simaishi, smallamp, stcannon, suppawar, syedriko, tguha, thason, twaugh, veshanka, vkumar, watson-tool-maintainers, weaton, xdharmai, yguenane, ykashtan, zhunting
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Pydantic. When an application validates structured data types configured to permit extra attributes, a remote attacker can bypass data validation by supplying both a field's defined name and its alias. In this scenario, the application treats the field name as an extra attribute, causing the unvalidated value to overwrite the validated data. This failure allows untrusted or malformed input to pass into downstream application logic without proper verification.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2578014, 2578015    
Bug Blocks:    

Description OSIDB Bzimport 2026-11-20 07:41:43 UTC
When extra data is allowed, providing both the alias and the name of an aliased TypedDict or dataclass field makes the unvalidated value (provided under the name) overwrite the validated one (provided under the alias), resulting in validated data not matching the declared type.

Extra items are stored in the same dictionary as the fields (the returned dictionary for TypedDict, the instance __dict__ for dataclasses). As only the alias is marked as used, the field name is treated as an extra item, and its unvalidated value overrides the validated one. The TypedDict validator (pydantic-core/src/validators/typed_dict.rs) and the dataclass validator (pydantic-core/src/validators/dataclass.rs) share this logic.

The issue was fixed in commit 34491f5328f168f14e3769cd5f0f83c0af0f4778.

Impact: validation bypass, as data returned by validation doesn't match the declared type. Affected are applications validating untrusted data into TypedDict or dataclass types with aliased fields and extra data allowed (with extra='allow', or with the extra_items argument for TypedDict), using Pydantic V2 (up to and including 2.14.1).

Pydantic models (BaseModel) are not affected, as extra data is stored separately from fields.