jackson-databind: @JsonIgnore on a Record property is bypassed with a PropertyNamingStrategy
Published 21 Jul 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
- >=2.15.0 <2.18.8
- Fixed in
- 2.18.8
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.18.8 -DforceVersion=true- Affected
- >=2.19.0 <2.21.4
- Fixed in
- 2.21.4
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
mvn versions:use-dep-version -Dincludes=tools.jackson.core:jackson-databind -DdepVersion=3.1.4 -DforceVersion=trueDetails
Summary
For Java Records, POJOPropertiesCollector._removeUnwantedIgnorals() records a @JsonIgnore-annotated component under its original implicit name before _renameUsing() applies the PropertyNamingStrategy. After the rename, _ignoredPropertyNames still holds only the pre-rename name, so _ignorableProps is built from the stale key. The renamed JSON key passes IgnorePropertiesUtil.shouldIgnore() and is assigned to the Record's constructor parameter, defeating the @JsonIgnore.
Impact
A Record using a naming strategy that relies on @JsonIgnore to 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-2.18 line:
>= 2.15.0, < 2.18.8-> fixed in 2.18.8 (backportc7c6783) - 2.19-2.21 line:
>= 2.19.0, < 2.21.4-> fixed in 2.21.4 - 3.x line:
>= 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.
Is GHSA-3pjw-73gf-8qr5 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-3pjw-73gf-8qr5
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-59888
- Linkgithub.com/FasterXML/jackson-databind/pull/5974
- Linkgithub.com/FasterXML/jackson-databind/commit/baa2cdf5ca2b2717fbb88d91955d69d8651df3e4
- Linkgithub.com/FasterXML/jackson-databind/commit/c7c678360624da5bc7eed2152789fa522880db9d
- Packagegithub.com/FasterXML/jackson-databind
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.