jackson-databind has case-insensitive deserialization bypasses per-property @JsonIgnoreProperties
CVE-2026-54515GHSA-5jmj-h7xm-6q6v
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (tools.jackson.core:jackson-databind 3.1.4; com.fasterxml.jackson.core:jackson-databind 3.1.4, 2.22.1, 2.21.5, 2.18.9), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven tools.jackson.core:jackson-databind
- Affected
- >= 3.1.0, < 3.1.4
- Fixed in
- 3.1.4
Maven com.fasterxml.jackson.core:jackson-databind
- Affected
- >= 3.1.0, < 3.1.4>= 2.8.0, < 2.18.9>= 2.19.0, < 2.21.5>= 2.22.0, < 2.22.1
- Fixed in
- 2.22.1, 2.21.5, 2.18.9, 3.1.4
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-5jmj-h7xm-6q6v lists affected ranges: Maven com.fasterxml.jackson.core:jackson-databind >=3.1.0 =2.8.0 =2.19.0 =2.22.0 =3.1.0 <3.1.4
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- EPSS
- CVE-2026-54515: 0.44% estimated exploitation activity in the next 30 days; percentile 38.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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(ACCEPTCASEINSENSITIVEPROPERTIES)) 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,…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-5jmj-h7xm-6q6v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-54515 Advisory: jackson-databind has case-insensitive deserialization bypasses per-property @JsonIgnoreProperties IDs: CVE-2026-54515, GHSA-5jmj-h7xm-6q6v Record: https://patchnext.com/advisories/cve-2026-54515 (revision 1, source checked 26 Oct 2026, 16:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: tools.jackson.core:jackson-databind 3.1.4; com.fasterxml.jackson.core:jackson-databind 3.1.4, 2.22.1, 2.21.5, 2.18.9. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven tools.jackson.core:jackson-databind: affected >= 3.1.0, < 3.1.4; fixed in 3.1.4 - Maven com.fasterxml.jackson.core:jackson-databind: affected >= 3.1.0, < 3.1.4; >= 2.8.0, < 2.18.9; >= 2.19.0, < 2.21.5; >= 2.22.0, < 2.22.1; fixed in 2.22.1, 2.21.5, 2.18.9, 3.1.4 ## Suggested inspection (read-only) - Maven tools.jackson.core:jackson-databind: check the installed version with your package manager. - Maven com.fasterxml.jackson.core:jackson-databind: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on tools.jackson.core:jackson-databind, com.fasterxml.jackson.core:jackson-databind. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-5jmj-h7xm-6q6v (GitHub-reviewed advisory GHSA-5jmj-h7xm-6q6v lists affected ranges: Maven com.fasterxml.jackson.core:jackson-databind >=3.1.0 =2.8.0 =2.19.0 =2.22.0 =3.1.0 <3.1.4) Commands are suggestions: review each one before running it.
Loading voting…