<?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, 24 Oct 2026 15:14:14 +0000</lastBuildDate>
    <item>
      <title>GHSA-3pjw-73gf-8qr5 — jackson-databind: @JsonIgnore on a Record property is bypassed with a PropertyNamingStrategy</title>
      <link>https://db.gcve.eu/vuln/ghsa-3pjw-73gf-8qr5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.fasterxml.jackson.core:jackson-databind, Maven: tools.jackson.core:jackson-databind&lt;/p&gt;
&lt;p&gt;## Summary
For Java Records, `POJOPropertiesCollector._removeUnwantedIgnorals()` records a `@JsonIgnore`-annotated component under its original implicit name before `_renameUsing()` applies the `PropertyNamingStrategy`. After the rename, `_ignoredPropertyNames` still holds only the pre-rename name, so `_ignorableProps` is built from the stale key. The renamed JSON key passes `IgnorePropertiesUtil.shouldIgnore()` and is assigned to the Record&amp;#39;s constructor parameter, defeating the `@JsonIgnore`.&lt;/p&gt;
&lt;p&gt;## Impact
A Record using a naming strategy that relies on `@JsonIgnore` to keep an internal/privileged component out of deserialization can have that component set from the wire via its renamed key (e.g. a role/flag controlled by an untrusted client).&lt;/p&gt;
&lt;p&gt;## Affected / Patched (verified via `git tag --contains`)
- 2.15-2.18 line: `&amp;gt;= 2.15.0, &amp;lt; 2.18.8` -&amp;gt; fixed in **2.18.8** (backport `c7c6783`)
- 2.19-2.21 line: `&amp;gt;= 2.19.0, &amp;lt; 2.21.4` -&amp;gt; fixed in **2.21.4**
- 3.x line: `&amp;gt;= 3.0.0, &amp;lt; 3.1.4` -&amp;gt; fixed in **3.1.4** (#5974, `baa2cdf`)&lt;/p&gt;
&lt;p&gt;## Severity / CWE
Maintainer: minor. Reporter: Moderate. CWE-915; related CWE-345.&lt;/p&gt;
&lt;p&gt;## Credits
Omkhar Arasaratnam (@omkhar) - finder.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.fasterxml.jackson.core:jackson-databind, Maven: tools.jackson.core:jackson-databind&lt;/p&gt;
&lt;p&gt;## Summary
For Java Records, `POJOPropertiesCollector._removeUnwantedIgnorals()` records a `@JsonIgnore`-annotated component under its original implicit name before `_renameUsing()` applies the `PropertyNamingStrategy`. After the rename, `_ignoredPropertyNames` still holds only the pre-rename name, so `_ignorableProps` is built from the stale key. The renamed JSON key passes `IgnorePropertiesUtil.shouldIgnore()` and is assigned to the Record&amp;#39;s constructor parameter, defeating the `@JsonIgnore`.&lt;/p&gt;
&lt;p&gt;## Impact
A Record using a naming strategy that relies on `@JsonIgnore` to keep an internal/privileged component out of deserialization can have that component set from the wire via its renamed key (e.g. a role/flag controlled by an untrusted client).&lt;/p&gt;
&lt;p&gt;## Affected / Patched (verified via `git tag --contains`)
- 2.15-2.18 line: `&amp;gt;= 2.15.0, &amp;lt; 2.18.8` -&amp;gt; fixed in **2.18.8** (backport `c7c6783`)
- 2.19-2.21 line: `&amp;gt;= 2.19.0, &amp;lt; 2.21.4` -&amp;gt; fixed in **2.21.4**
- 3.x line: `&amp;gt;= 3.0.0, &amp;lt; 3.1.4` -&amp;gt; fixed in **3.1.4** (#5974, `baa2cdf`)&lt;/p&gt;
&lt;p&gt;## Severity / CWE
Maintainer: minor. Reporter: Moderate. CWE-915; related CWE-345.&lt;/p&gt;
&lt;p&gt;## Credits
Omkhar Arasaratnam (@omkhar) - finder.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-3pjw-73gf-8qr5</guid>
    </item>
  </channel>
</rss>
