Com.fasterxml.jackson.core:jackson databind: jackson-databind: `@JsonView` bypass for creator properties with `@JsonTypeInfo(include=As.EXTERNAL_PROPERTY)`
A vulnerability in jackson-databind versions 2.18.0 through 2.18.8 and 2.21.0 through 2.21.4 allows bypassing the @JsonView filter for creator properties annotated with @JsonTypeInfo(include=As.EXTERNAL_PROPERTY). This occurs because the active view check is missing in the creator-property branch of the deserialization code, enabling attacker-controlled JSON to populate restricted properties even when a more restrictive view is active.
AI Analysis
Technical Summary
The vulnerability exists in the BeanDeserializer.deserializeUsingPropertyBasedWithExternalTypeId method of jackson-databind versions 2.18.0 to 2.18.8 and 2.21.0 to 2.21.4. The active-view (@JsonView) filter is applied only to the regular bean-property branch but not to the creator-property branch when @JsonTypeInfo is used with include=As.EXTERNAL_PROPERTY. This omission allows constructor parameters annotated with both @JsonView and @JsonTypeInfo to be populated from attacker JSON despite an active restrictive view. The issue was fixed in the 3.x line but the fix was not backported to the affected 2.18 and 2.21 versions. A proof-of-concept demonstrates that admin-only properties can be populated when deserializing with a public view, confirming the bypass.
Potential Impact
An attacker can bypass the intended @JsonView restrictions on creator properties when using @JsonTypeInfo with As.EXTERNAL_PROPERTY, potentially leading to unauthorized data exposure or manipulation of sensitive fields during JSON deserialization. This affects confidentiality and integrity of data processed by vulnerable jackson-databind versions.
Mitigation Recommendations
No official patch has been backported to the affected 2.18 and 2.21 versions. Users should upgrade to jackson-databind 3.x where the fix is implemented. Until then, avoid using @JsonView with creator properties annotated with @JsonTypeInfo(include=As.EXTERNAL_PROPERTY) in the vulnerable versions. Monitor vendor advisories for updates on backports or official fixes. Patch status is not yet confirmed for 2.18 and 2.21 branches; check vendor advisories for current remediation guidance.
Com.fasterxml.jackson.core:jackson databind: jackson-databind: `@JsonView` bypass for creator properties with `@JsonTypeInfo(include=As.EXTERNAL_PROPERTY)`
Description
A vulnerability in jackson-databind versions 2.18.0 through 2.18.8 and 2.21.0 through 2.21.4 allows bypassing the @JsonView filter for creator properties annotated with @JsonTypeInfo(include=As.EXTERNAL_PROPERTY). This occurs because the active view check is missing in the creator-property branch of the deserialization code, enabling attacker-controlled JSON to populate restricted properties even when a more restrictive view is active.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in the BeanDeserializer.deserializeUsingPropertyBasedWithExternalTypeId method of jackson-databind versions 2.18.0 to 2.18.8 and 2.21.0 to 2.21.4. The active-view (@JsonView) filter is applied only to the regular bean-property branch but not to the creator-property branch when @JsonTypeInfo is used with include=As.EXTERNAL_PROPERTY. This omission allows constructor parameters annotated with both @JsonView and @JsonTypeInfo to be populated from attacker JSON despite an active restrictive view. The issue was fixed in the 3.x line but the fix was not backported to the affected 2.18 and 2.21 versions. A proof-of-concept demonstrates that admin-only properties can be populated when deserializing with a public view, confirming the bypass.
Potential Impact
An attacker can bypass the intended @JsonView restrictions on creator properties when using @JsonTypeInfo with As.EXTERNAL_PROPERTY, potentially leading to unauthorized data exposure or manipulation of sensitive fields during JSON deserialization. This affects confidentiality and integrity of data processed by vulnerable jackson-databind versions.
Mitigation Recommendations
No official patch has been backported to the affected 2.18 and 2.21 versions. Users should upgrade to jackson-databind 3.x where the fix is implemented. Until then, avoid using @JsonView with creator properties annotated with @JsonTypeInfo(include=As.EXTERNAL_PROPERTY) in the vulnerable versions. Monitor vendor advisories for updates on backports or official fixes. Patch status is not yet confirmed for 2.18 and 2.21 branches; check vendor advisories for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mhm7-754m-9p8w
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["Maven"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a600ac39c2644c7f8fe33c8
Added to database: 07/22/2026, 00:11:47 UTC
Last enriched: 07/22/2026, 00:56:11 UTC
Last updated: 07/22/2026, 01:44:11 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.