CVE-2026-54516: CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes in FasterXML jackson-databind
jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, POJOPropertiesCollector._renameProperties() allows a property with @JsonProperty("renamed") on the getter and @JsonIgnore on the setter to be renamed rather than dropped. With MapperFeature.INFER_PROPERTY_MUTATORS enabled (default), the private backing field is retained; during deserialization BeanDeserializerFactory.addBeanProps() sees hasField()==true, builds a FieldProperty, and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the @JsonIgnore on the setter. This vulnerability is fixed in 3.1.4.
AI Analysis
Technical Summary
CVE-2026-54516 is a medium severity vulnerability in jackson-databind affecting versions >=2.21.0 and <3.1.4. The flaw arises in POJOPropertiesCollector._renameProperties(), where a property annotated with @JsonProperty("renamed") on the getter and @JsonIgnore on the setter is renamed instead of dropped. With the default MapperFeature.INFER_PROPERTY_MUTATORS enabled, the private backing field remains accessible. During deserialization, BeanDeserializerFactory.addBeanProps() detects the field and creates a writable FieldProperty, allowing an attacker to supply a renamed JSON key that writes directly to the backing field, bypassing the setter's @JsonIgnore protection. This can lead to improper modification of object attributes. The vulnerability is resolved in version 3.1.4.
Potential Impact
An attacker can bypass the @JsonIgnore annotation on setter methods by directly modifying private backing fields during deserialization, potentially leading to unauthorized modification of object attributes. The vulnerability does not impact confidentiality or availability but can cause integrity issues by allowing injection of unexpected data into objects.
Mitigation Recommendations
A fix is available in jackson-databind version 3.1.4. Users should upgrade to version 3.1.4 or later to remediate this vulnerability. Patch status is not explicitly stated beyond this fix version, so users should verify with the vendor advisory for the latest remediation guidance.
CVE-2026-54516: CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes in FasterXML jackson-databind
Description
jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, POJOPropertiesCollector._renameProperties() allows a property with @JsonProperty("renamed") on the getter and @JsonIgnore on the setter to be renamed rather than dropped. With MapperFeature.INFER_PROPERTY_MUTATORS enabled (default), the private backing field is retained; during deserialization BeanDeserializerFactory.addBeanProps() sees hasField()==true, builds a FieldProperty, and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the @JsonIgnore on the setter. This vulnerability is fixed in 3.1.4.
CVSS v3.1
Score 5.3medium
Affected software
pkg:maven/com.fasterxml.jackson.core/jackson-databindRun 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
CVE-2026-54516 is a medium severity vulnerability in jackson-databind affecting versions >=2.21.0 and <3.1.4. The flaw arises in POJOPropertiesCollector._renameProperties(), where a property annotated with @JsonProperty("renamed") on the getter and @JsonIgnore on the setter is renamed instead of dropped. With the default MapperFeature.INFER_PROPERTY_MUTATORS enabled, the private backing field remains accessible. During deserialization, BeanDeserializerFactory.addBeanProps() detects the field and creates a writable FieldProperty, allowing an attacker to supply a renamed JSON key that writes directly to the backing field, bypassing the setter's @JsonIgnore protection. This can lead to improper modification of object attributes. The vulnerability is resolved in version 3.1.4.
Potential Impact
An attacker can bypass the @JsonIgnore annotation on setter methods by directly modifying private backing fields during deserialization, potentially leading to unauthorized modification of object attributes. The vulnerability does not impact confidentiality or availability but can cause integrity issues by allowing injection of unexpected data into objects.
Mitigation Recommendations
A fix is available in jackson-databind version 3.1.4. Users should upgrade to version 3.1.4 or later to remediate this vulnerability. Patch status is not explicitly stated beyond this fix version, so users should verify with the vendor advisory for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-15T18:40:01.650Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3af602eed863c81e9ec640
Added to database: 06/23/2026, 21:09:22 UTC
Last enriched: 06/30/2026, 23:21:06 UTC
Last updated: 08/07/2026, 12:41:12 UTC
Views: 85
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.