<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 22:34:32 +0000</lastBuildDate>
    <item>
      <title>GHSA-mhm7-754m-9p8w — jackson-databind: `@JsonView` bypass for creator properties with `@JsonTypeInfo(include=As.EXTERNAL_PROPERTY)`</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-mhm7-754m-9p8w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.fasterxml.jackson.core:jackson-databind&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;In `BeanDeserializer.deserializeUsingPropertyBasedWithExternalTypeId`, the active-view (`@JsonView`) filter was applied only to the regular bean-property branch; the creator-property branch performed no `creatorProp.visibleInView(activeView)` check. A constructor parameter annotated with both `@JsonView(RestrictedView.class)` and `@JsonTypeInfo(use=Id.NAME,
  include=As.EXTERNAL_PROPERTY)` is populated from attacker JSON even when a more restrictive view is active.&lt;/p&gt;
&lt;p&gt;This is a patch gap. GHSA-5hh8 (CVE-2026-54517) and GHSA-rcqc (CVE-2026-54518) descriptions cover only the main property-based path and the unwrapped-creator path respectively; the external-type-id creator path was fixed on the 3.x line via #6004 (&amp;#34;Extend #5969/#5971 fixes to ... external-type-id case in regular BeanDeserializer&amp;#34;, commit 7dc7a17, 2026-05-22) but
  **the fix was never backported to 2.21 or 2.18**. Users on 2.21.4 and 2.18.8 who upgraded per the published advisories remain vulnerable to the same `@JsonView` bypass technique via a different code path.&lt;/p&gt;
&lt;p&gt;## Vulnerable Code Path&lt;/p&gt;
&lt;p&gt;File: `com/fasterxml/jackson/databind/deser/BeanDeserializer.java`
Method: `deserializeUsingPropertyBasedWithExternalTypeId`&lt;/p&gt;
&lt;p&gt;On 2.21.4 (and 2.18.8), the creator-property branch (around line 1125-1158) checks `creatorProp.isInjectionOnly()` and hands off to `ext.handlePropertyValue(...)` / `buffer.assignParameter(...)` without ever consulting `visibleInView(activeView)`:&lt;/p&gt;
&lt;p&gt;```java
  if (creatorProp != null) {…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.fasterxml.jackson.core:jackson-databind&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;In `BeanDeserializer.deserializeUsingPropertyBasedWithExternalTypeId`, the active-view (`@JsonView`) filter was applied only to the regular bean-property branch; the creator-property branch performed no `creatorProp.visibleInView(activeView)` check. A constructor parameter annotated with both `@JsonView(RestrictedView.class)` and `@JsonTypeInfo(use=Id.NAME,
  include=As.EXTERNAL_PROPERTY)` is populated from attacker JSON even when a more restrictive view is active.&lt;/p&gt;
&lt;p&gt;This is a patch gap. GHSA-5hh8 (CVE-2026-54517) and GHSA-rcqc (CVE-2026-54518) descriptions cover only the main property-based path and the unwrapped-creator path respectively; the external-type-id creator path was fixed on the 3.x line via #6004 (&amp;#34;Extend #5969/#5971 fixes to ... external-type-id case in regular BeanDeserializer&amp;#34;, commit 7dc7a17, 2026-05-22) but
  **the fix was never backported to 2.21 or 2.18**. Users on 2.21.4 and 2.18.8 who upgraded per the published advisories remain vulnerable to the same `@JsonView` bypass technique via a different code path.&lt;/p&gt;
&lt;p&gt;## Vulnerable Code Path&lt;/p&gt;
&lt;p&gt;File: `com/fasterxml/jackson/databind/deser/BeanDeserializer.java`
Method: `deserializeUsingPropertyBasedWithExternalTypeId`&lt;/p&gt;
&lt;p&gt;On 2.21.4 (and 2.18.8), the creator-property branch (around line 1125-1158) checks `creatorProp.isInjectionOnly()` and hands off to `ext.handlePropertyValue(...)` / `buffer.assignParameter(...)` without ever consulting `visibleInView(activeView)`:&lt;/p&gt;
&lt;p&gt;```java
  if (creatorProp != null) {…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-mhm7-754m-9p8w</guid>
    </item>
  </channel>
</rss>
