MediumGHSA-9fxm-vc8v-hj55CVE-2026-54516

jackson-databind's renamed @JsonIgnore'd setters can deserialize via private fields

Published 23 Jun 2026 · Updated 10 Sept 2026

Is your project on an affected com.fasterxml.jackson.core:jackson-databind?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.21.0 <2.21.4
Fixed in
2.21.4
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.21.4 -DforceVersion=true
Affected
>=3.0.0 <3.1.4
Fixed in
3.1.4
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=3.1.4 -DforceVersion=true
Affected
>=3.0.0 <3.1.4
Fixed in
3.1.4
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=tools.jackson.core:jackson-databind -DdepVersion=3.1.4 -DforceVersion=true

Details

Summary

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.

Impact

POJOs combining a renamed getter with an ignored setter (a read-only-over-the-wire pattern) have that field silently set from attacker input (property tampering / mass assignment). Not a general gadget; no RCE.

Affected / Patched (verified via git tag --contains)

  • 2.21 line: >= 2.21.0, < 2.21.4 -> fixed in 2.21.4 (backport c3d56dd, #5968)
  • 3.x line: >= 3.0.0, < 3.1.4 -> fixed in 3.1.4 (#5967, e88cb17)

Severity / CWE

Maintainer: minor. Reporter: HIGH. CWE-915.

Credits

Omkhar Arasaratnam (@omkhar) - finder.

Is GHSA-9fxm-vc8v-hj55 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
All 86 advisories for com.fasterxml.jackson.core:jackson-databind

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.