<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 04:58:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-133429 — Validation bypass of extra data keys in JSON model validation</title>
      <link>https://db.gcve.eu/vuln/cve-2026-133429</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pydantic&lt;/p&gt;
&lt;p&gt;When validating JSON data into a model allowing extra data, the keys of extra data aren&amp;#39;t validated against the key type annotated on __pydantic_extra__, resulting in extra data not matching the declared type. This is the case if you define __pydantic_extra__ as e.g. dict[Annotated[str, Field(pattern=r&amp;#39;^x_&amp;#39;)], int].&lt;/p&gt;
&lt;p&gt;The validate_json_by_iteration() method (in pydantic-core/src/validators/model_fields.rs), used to validate JSON data into models, only validates the values of extra data, and stores the keys as is.&lt;/p&gt;
&lt;p&gt;The issue was fixed in commit 4c65dbda9970a488e2ff21c8693fc6f6d70a3358.&lt;/p&gt;
&lt;p&gt;Impact: validation bypass, as extra data returned by validation doesn&amp;#39;t match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with extra=&amp;#39;allow&amp;#39;), with a key type annotated on __pydantic_extra__ (e.g. dict[Annotated[str, Field(pattern=...)], int]), using Pydantic from 2.13.0 up to (but excluding) 2.14.2.&lt;/p&gt;
&lt;p&gt;Python mode validation isn&amp;#39;t affected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pydantic&lt;/p&gt;
&lt;p&gt;When validating JSON data into a model allowing extra data, the keys of extra data aren&amp;#39;t validated against the key type annotated on __pydantic_extra__, resulting in extra data not matching the declared type. This is the case if you define __pydantic_extra__ as e.g. dict[Annotated[str, Field(pattern=r&amp;#39;^x_&amp;#39;)], int].&lt;/p&gt;
&lt;p&gt;The validate_json_by_iteration() method (in pydantic-core/src/validators/model_fields.rs), used to validate JSON data into models, only validates the values of extra data, and stores the keys as is.&lt;/p&gt;
&lt;p&gt;The issue was fixed in commit 4c65dbda9970a488e2ff21c8693fc6f6d70a3358.&lt;/p&gt;
&lt;p&gt;Impact: validation bypass, as extra data returned by validation doesn&amp;#39;t match the declared type. Affected are applications validating untrusted JSON data into models allowing extra data (with extra=&amp;#39;allow&amp;#39;), with a key type annotated on __pydantic_extra__ (e.g. dict[Annotated[str, Field(pattern=...)], int]), using Pydantic from 2.13.0 up to (but excluding) 2.14.2.&lt;/p&gt;
&lt;p&gt;Python mode validation isn&amp;#39;t affected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-133429</guid>
    </item>
  </channel>
</rss>
