jackson-databind has case-insensitive deserialization bypasses per-property @JsonIgnoreProperties
Published 23 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected com.fasterxml.jackson.core:jackson-databind?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=3.1.0 <3.1.4
- Fixed in
- 3.1.4
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=3.1.4 -DforceVersion=true- Affected
- >=3.1.0 <3.1.4
- Fixed in
- 3.1.4
mvn versions:use-dep-version -Dincludes=tools.jackson.core:jackson-databind -DdepVersion=3.1.4 -DforceVersion=true- Affected
- >=2.8.0 <2.18.9
- Fixed in
- 2.18.9
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.18.9 -DforceVersion=true- Affected
- >=2.19.0 <2.21.5
- Fixed in
- 2.21.5
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.21.5 -DforceVersion=true- Affected
- >=2.22.0 <2.22.1
- Fixed in
- 2.22.1
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.22.1 -DforceVersion=trueDetails
Summary
In BeanDeserializerBase.createContextual(), per-property @JsonIgnoreProperties exclusions are applied by _handleByNameInclusion(), producing a contextual deserializer whose BeanPropertyMap has the ignored properties removed. The subsequent per-property case-insensitivity block (triggered by @JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) rebuilds from this._beanProperties (the original, unfiltered map) instead of contextual._beanProperties, then overwrites the filtered map — restoring every property _handleByNameInclusion had just removed. The ignored property becomes writable again.
Impact
An application that both enables case-insensitive matching and relies on per-property @JsonIgnoreProperties to 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.
Is GHSA-5jmj-h7xm-6q6v in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected com.fasterxml.jackson.core:jackson-databind, and gives you the command that fixes it.
More advisories for com.fasterxml.jackson.core:jackson-databind
- HighCVE-2026-91777jackson-databind quadratic forward-reference completion · 30 Sept 2026
- HighCVE-2026-91776jackson-databind retains every unknown raw type ID · 30 Sept 2026
- MediumCVE-2026-83557jackson-databind: Comparable missing from DefaultBaseTypeLimitingValidator's unsafe base types (incomplete PolymorphicTypeValidator denylist) · 28 Sept 2026
- HighCVE-2026-68497jackson-databind: Duration XMLGregorianCalendar Unbounded Number Parse DoS · 28 Sept 2026
- MediumCVE-2026-19032jackson-databind: Path Deserialization Missing Scheme Allowlist for FileSystemProvider Resolution · 28 Sept 2026
- MediumCVE-2026-77310jackson-databind: Incomplete fix for CVE-2026-54514: eager DNS resolution (SSRF) still present in InetAddress deserialization · 28 Sept 2026
References
- Linkgithub.com/FasterXML/jackson-databind/security/advisories/GHSA-5jmj-h7xm-6q6v
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-54515
- Linkgithub.com/FasterXML/jackson-databind/issues/5962
- Linkgithub.com/FasterXML/jackson-databind/issues/5964
- Linkgithub.com/FasterXML/jackson-databind/commit/0e1b0b211f7a53baa62ba2f4c9bd006c7bf4d5fa
- Packagegithub.com/FasterXML/jackson-databind
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.