fix(deps): update dependency com.fasterxml.jackson.core:jackson-databind to v2.22.1 [security]#342
Merged
descope[bot] merged 1 commit intoJul 23, 2026
Conversation
descope
Bot
force-pushed
the
renovate/maven-com.fasterxml.jackson.core-jackson-databind-vulnerability
branch
from
July 23, 2026 22:17
5c2b55a to
11a96ec
Compare
…ind to v2.22.1 [security]
descope
Bot
force-pushed
the
renovate/maven-com.fasterxml.jackson.core-jackson-databind-vulnerability
branch
from
July 23, 2026 22:40
11a96ec to
e6c80e3
Compare
descope
Bot
deleted the
renovate/maven-com.fasterxml.jackson.core-jackson-databind-vulnerability
branch
July 23, 2026 22:51
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.22.0→2.22.1jackson-databind has a PolymorphicTypeValidator bypass via generic type parameters that allows arbitrary class instantiation
CVE-2026-54512 / GHSA-j3rv-43j4-c7qm
More information
Details
jackson-databind'sPolymorphicTypeValidator(PTV) is the primary safety mechanism guarding polymorphic deserialization. When polymorphic typing is enabled and a type identifier contains generic parameters (i.e. the type ID string contains<),DatabindContext._resolveAndValidateGeneric()validates only the raw container class name (the substring before<) against the configured PTV.If the container type is approved, the method parses the full canonical type string via
TypeFactory.constructFromCanonical()and returns the fully parameterized type without ever validating the nested type arguments against the PTV. The nested type arguments are then resolved, instantiated, and populated as beans during deserialization.An attacker who controls the type ID can therefore place a denied class as a generic type parameter of an allowed container — for example
java.util.ArrayList<com.evil.Gadget>when onlyjava.util.ArrayListis allow-listed. The container passes the PTV check;com.evil.Gadgetis loaded viaClass.forName(name, true, loader), instantiated, and its properties are set from attacker-controlled JSON. This completely bypasses an explicitly configured PTV allow-list.This is the same vulnerability class responsible for the historical sequence of jackson-databind deserialization CVEs; here it manifests as a validator bypass rather than a missing deny-list entry.
Impact
BasicPolymorphicTypeValidatorconfigured with name-prefix allow rules.TemplatesImpl-style loaders, etc.) is present on the classpath.Applications that accept untrusted JSON and rely on a configured PTV — the documented, security-conscious configuration — are affected.
Proof of Concept
Configuration restricting polymorphic deserialization to a single safe container:
Malicious payload (
Wrapper.valueisObjectwith@JsonTypeInfo(use = Id.CLASS, include = As.WRAPPER_ARRAY)):{"value":["java.util.ArrayList<com.evil.EvilGadget>",[{"cmd":"calc.exe"}]]}On vulnerable versions,
com.evil.EvilGadgetis instantiated and itscmdproperty is set, despite onlyjava.util.ArrayListbeing allow-listed. On2.18.8/2.21.4/3.1.4the deserialization throwsInvalidTypeIdExceptionbefore instantiation.Variant payloads (all bypass an
ArrayList/HashMapallow-list):java.util.ArrayList<Evil>java.util.HashMap<Evil,String>java.util.HashMap<String,Evil>java.util.ArrayList<java.util.ArrayList<Evil>>java.util.ArrayList<Evil[]>Patches
Fixed in 2.18.8, 2.21.4 and 3.1.4 via the changes for FasterXML/jackson-databind#5988, commit
434d6c511. The fix adds recursive validation of each non-trivial type parameter (and array element types appearing as parameters) through the full PTV chain, with documented exemptions forObject(wildcard resolution) andEnumtypes.PolymorphicTypeValidatorwas added in 2.10.0 so vulnerability N/A for versions prior to that.Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
jackson-databind has an array subtype allowlist bypass in BasicPolymorphicTypeValidator (allowIfSubTypeIsArray)
CVE-2026-54513 / GHSA-rmj7-2vxq-3g9f
More information
Details
Summary
BasicPolymorphicTypeValidator.Builder.allowIfSubTypeIsArray()allowlists any array type based only onclazz.isArray(), without validating the array's component (element) type against the configured allowlist. A PTV built withallowIfSubTypeIsArray()plus an explicit concrete-type allowlist therefore still permitsEvilType[]even thoughEvilTypeis not allowlisted. When Jackson deserializes the elements and no per-element type IDs are present, it instantiates the component type directly with no further PTV check, bypassing the allowlist.Impact
Applications using
BasicPolymorphicTypeValidatorwithallowIfSubTypeIsArray()as a safeguard get no protection for concrete array component types; an attacker controlling JSON can instantiate non-allowlisted types via an array wrapper, re-opening the gadget-instantiation risk PTV is meant to prevent.Affected / Patched (verified via
git tag --contains)>= 2.10.0, < 2.18.8-> fixed in 2.18.8>= 2.19.0, < 2.21.4-> fixed in 2.21.4>= 3.0.0, < 3.1.4-> fixed in 3.1.4PolymorphicTypeValidatorwas added in 2.10.0 so vulnerability N/A for versions prior to that.Severity / CWE
Maintainer: significant. Reporter: HIGH. CWE-184 (Incomplete List of Disallowed Inputs); related CWE-502.
Upstream fix
FasterXML/jackson-databind#5981; fix PR #5983 (
24529da), 2.18 backport PR #5984 (01d1692). Released 2026-06-04 in 2.18.8 / 2.21.4 / 3.1.4.Credits
Omkhar Arasaratnam (@omkhar) - finder.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
jackson-databind: InetSocketAddress deserialization triggers eager DNS resolution (SSRF)
CVE-2026-54514 / GHSA-hgj6-7826-r7m5
More information
Details
Summary
JDKFromStringDeserializerconstructedInetSocketAddresswithnew InetSocketAddress(host, port), which performs eager DNS name resolution for hostname inputs at deserialization time. An application that binds untrusted JSON into a type containing anInetSocketAddressfield issues an attacker-chosen DNS query duringreadValue, before any application-level validation or connect logic. The fix usesInetSocketAddress.createUnresolved(host, port), deferring DNS to an explicit connect.Impact
An attacker controlling JSON deserialized into an
InetSocketAddress-bearing type can force outbound DNS lookups for attacker-chosen hostnames at deserialization time (SSRF / DNS-based out-of-band interaction / internal-resolver probing), purely from binding.Affected / Patched (verified via
git tag --containson1f5a103)>= 2.18.0, < 2.18.8-> fixed in 2.18.8>= 2.19.0, < 2.21.4-> fixed in 2.21.4>= 3.0.0, < 3.1.4-> fixed in 3.1.4Severity / CWE
Maintainer: minor. Reporter: LOW. CWE-918 (SSRF).
Upstream fix
FasterXML/jackson-databind#5951 ("Improve InetSocketAddress deserialization"). Released 2026-06-04 in 2.18.8 / 2.21.4 / 3.1.4.
Credits
Omkhar Arasaratnam (@omkhar) - finder.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
jackson-databind has case-insensitive deserialization bypasses per-property @JsonIgnoreProperties
CVE-2026-54515 / GHSA-5jmj-h7xm-6q6v
More information
Details
Summary
In
BeanDeserializerBase.createContextual(), per-property@JsonIgnorePropertiesexclusions are applied by_handleByNameInclusion(), producing acontextualdeserializer whoseBeanPropertyMaphas the ignored properties removed. The subsequent per-property case-insensitivity block (triggered by@JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) rebuilds fromthis._beanProperties(the original, unfiltered map) instead ofcontextual._beanProperties, then overwrites the filtered map — restoring every property_handleByNameInclusionhad just removed. The ignored property becomes writable again.Impact
An application that both enables case-insensitive matching and relies on per-property
@JsonIgnorePropertiesto keep a field unwritable can have that field set from untrusted JSON (mass-assignment-style write).Affected / Patched
Will be fixed in 2.18.9, 2.21.5, 2.22.1 and 3.1.4.
Severity / CWE
Maintainer: minor. Reporter: Moderate. CWE-915.
Upstream fix
FasterXML/jackson-databind#5962 (PR #5964,
0e1b0b2), milestone 3.1.4. Released 2026-06-04.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
jackson-databind: @JsonIgnore on a Record property is bypassed with a PropertyNamingStrategy
CVE-2026-59888 / GHSA-3pjw-73gf-8qr5
More information
Details
Summary
For Java Records,
POJOPropertiesCollector._removeUnwantedIgnorals()records a@JsonIgnore-annotated component under its original implicit name before_renameUsing()applies thePropertyNamingStrategy. After the rename,_ignoredPropertyNamesstill holds only the pre-rename name, so_ignorablePropsis built from the stale key. The renamed JSON key passesIgnorePropertiesUtil.shouldIgnore()and is assigned to the Record's constructor parameter, defeating the@JsonIgnore.Impact
A Record using a naming strategy that relies on
@JsonIgnoreto 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).Affected / Patched (verified via
git tag --contains)>= 2.15.0, < 2.18.8-> fixed in 2.18.8 (backportc7c6783)>= 2.19.0, < 2.21.4-> fixed in 2.21.4>= 3.0.0, < 3.1.4-> fixed in 3.1.4 (#5974,baa2cdf)Severity / CWE
Maintainer: minor. Reporter: Moderate. CWE-915; related CWE-345.
Credits
Omkhar Arasaratnam (@omkhar) - finder.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
jackson-databind: @JsonView ypassed for @JsonUnwrapped container properties on deserialization
CVE-2026-59889 / GHSA-5gvw-p9qm-jgwh
More information
Details
Summary
UnwrappedPropertyHandler.processUnwrapped()replays the buffered JSON for a@JsonUnwrappedproperty by iterating its properties and callingprop.deserializeAndSet()with noprop.visibleInView(ctxt.getActiveView())guard — the exact guardprocessUnwrappedCreatorProperties()received in the #5971 / GHSA-rcqc-6cw3-h962 fix, and the guardBeanDeserializer.deserializeWithUnwrappedapplies to directly-matched properties. As a result, a property annotated with both@JsonView(PrivilegedView.class)and@JsonUnwrappedis written from attacker JSON even when deserializing under a more-restrictive active view.Correction to the original framing (runtime-verified): the gap is NOT a per-field inner
@JsonView(the unwrapped sub-object's ownBeanDeserializergates inner fields correctly). The unchecked gate is the view of the unwrapped CONTAINER property.Intent proof (runtime, 2.x HEAD 21dd70dd and 3.x HEAD 7a5939d6)
An
@JsonView(AdminView)property that is NOT@JsonUnwrapped→nullunderPublicView(correctly gated). The identical property WITH@JsonUnwrapped→ fully populated (bypass). The fix the creator path already received, not applied to the regular-property method.Impact — write-side mass-assignment / privilege escalation
@JsonViewis commonly used as a write-side authorization guard: a public endpoint binds the body underreaderWithView(PublicView.class)and groups privileged state in a nested object whose container property is@JsonView(AdminView). When that property is@JsonUnwrapped, an untrusted caller mass-assigns it. PoC: a self-service registration whereAccountFlags{role,approved,creditBalance}is@JsonView(AdminView) @​JsonUnwrapped; attacker JSON{role:ADMIN,approved:true,creditBalance:1000000}underPublicViewbinds all three → approved admin with arbitrary balance. The failing gate is a WRITE gate, hence integrity-high (C:N/I:H/A:N); no worse than the C:L/I:L parent and arguably higher as@JsonView-as-write-guard is the exact use case #5971/#5969 defended.Affected
com.fasterxml.jackson.core:jackson-databind2.x: confirmed bypass at 21dd70dd (== released 2.21.4 / 2.22.0 line; includes the #5973 backport).DEFAULT_VIEW_INCLUSIONdefault=true.tools.jackson.core:jackson-databind3.x: confirmed bypass at HEAD 7a5939d6 (latest 3.x).DEFAULT_VIEW_INCLUSIONdefault=false → the stock-config repro is the common shape where privileged inner fields are individually@JsonView(PublicView)and the developer relies on the container@JsonView(AdminView); the 3.x PoC mass-assigns role/approved/creditBalance under PublicView. (The other simultaneous report's PoC was reportedly fixed on 3.x; this distinct container-property path is not.)Additive variants (runtime-confirmed both branches; all closed by the same one-line guard)
@JsonUnwrapped(unwrapped-in-unwrapped) — recursive bypass.readerWithView(...).withValueToUpdate(...)(PATCH/partial-update) — bypass; non-unwrapped merge control gates correctly.@JsonDeserialize(builder=...)) —BuilderBasedDeserializerroutes through the sameprocessUnwrapped.@JsonAnySetter+view and@JsonTypeInfo+@JsonUnwrappedare separate/unsupported behaviors, not this bug.Fix
Add
prop.visibleInView(ctxt.getActiveView())(whenMapperFeature.DEFAULT_VIEW_INCLUSION/active-view applies) to theprocessUnwrapped()property loop, mirroringprocessUnwrappedCreatorProperties(). One change closes the impact PoC + all three variants acrossBeanDeserializerandBuilderBasedDeserializer. Full runnable PoCs (2.x + 3.x) + variant harnesses available on request.Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
jackson-databind has case-insensitive deserialization bypasses per-property @JsonIgnoreProperties
CVE-2026-54515 / GHSA-5jmj-h7xm-6q6v
More information
Details
Summary
In
BeanDeserializerBase.createContextual(), per-property@JsonIgnorePropertiesexclusions are applied by_handleByNameInclusion(), producing acontextualdeserializer whoseBeanPropertyMaphas the ignored properties removed. The subsequent per-property case-insensitivity block (triggered by@JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) rebuilds fromthis._beanProperties(the original, unfiltered map) instead ofcontextual._beanProperties, then overwrites the filtered map — restoring every property_handleByNameInclusionhad just removed. The ignored property becomes writable again.Impact
An application that both enables case-insensitive matching and relies on per-property
@JsonIgnorePropertiesto keep a field unwritable can have that field set from untrusted JSON (mass-assignment-style write).Affected / Patched
Will be fixed in 2.18.9, 2.21.5, 2.22.1 and 3.1.4.
Severity / CWE
Maintainer: minor. Reporter: Moderate. CWE-915.
Upstream fix
FasterXML/jackson-databind#5962 (PR #5964,
0e1b0b2), milestone 3.1.4. Released 2026-06-04.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (in timezone Asia/Jerusalem)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.