ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-54516

Renamed @JsonIgnore'd setters can deserialize via private fields in jackson-databind

Published Jun 16, 2026 · catalog updated Oct 16, 2026 · Renamed @JsonIgnore'd setters can

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-54516. EPSS is 0.45%. Act only if a listed version of Renamed @JsonIgnore'd setters can is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Renamed @JsonIgnore'd setters can).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.45%
Remediation
Version ranges on file
Affected products
maven com.fasterxml.jackson.core:jackson-databind · maven tools.jackson.core:jackson-databind

## Summary allows a property with on the getter and on the setter to be renamed rather than dropped. With enabled (default), the private backing field is retained; during deserialization sees , builds a , and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the 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 ) - 2.21 line: -> fixed in **2.21.4** (backport , #5968) - 3.x line: -> fixed in **3.1.4** (#5967, ) ## Severity / CWE Maintainer: minor. Reporter: HIGH. CWE-915. ## Credits Omkhar Arasaratnam (@omkhar) - finder.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • maven com.fasterxml.jackson.core:jackson-databind>= 2.0.0, <= 2.18.11
  • maven com.fasterxml.jackson.core:jackson-databind>= 2.21.0, < 2.21.4
  • maven tools.jackson.core:jackson-databind>= 3.0.0, < 3.1.4

How to fix CVE-2026-54516

  • Upgrade

    CVE-2026-54516 lists a fix boundary at 2.18.11. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <= 2.18.11

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-54516. EPSS is 0.45%. Act only if a listed version of Renamed @JsonIgnore'd setters can is installed.

Which versions are affected?

Compare what you have installed with >= 2.0.0, <= 2.18.11, >= 2.21.0, < 2.21.4, >= 3.0.0, < 3.1.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes. EPSS 0.45%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Jackson security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 16, 2026 · Maintainer security tabs

    Detected

    ## Summary allows a property with on the getter and on the setter to be renamed rather than dropped. With enabled (default), the private backing field is retained; during deserialization sees , builds a , and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the on the setter. ## Impact POJOs combining a renamed getter with an

  2. Oct 16, 2026 · Maintainer security tabs

    Updated

    ## Summary allows a property with on the getter and on the setter to be renamed rather than dropped. With enabled (default), the private backing field is retained; during deserialization sees , builds a , and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the on the setter. ## Impact POJOs combining a renamed getter with an

Sources

  • Maintainer security tabsVendor advisoryGHSA-9fxm-vc8v-hj55

    ## Summary allows a property with on the getter and on the setter to be renamed rather than dropped. With enabled (default), the private backing field is retained; during deserialization sees , builds a , and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the on the setter. ## Impact POJOs combining a renamed getter with an

    github.com

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026