Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-59888: jackson-databind: @JsonIgnore on a Record property is bypassed with a PropertyNamingStrategy

MediumCVSS 6.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: com.fasterxml.jackson.core:jackson-databind (Maven) 2.18.8, 2.21.4; tools.jackson.core:jackson-databind (Maven) 3.1.4; jackson-annotations (openSUSE:Leap 16.0) 2.18.9-160000.1.1.

Low priority for now. Upgrade to com.fasterxml.jackson.core:jackson-databind (Maven) 2.18.8, 2.21.4; tools.jackson.core:jackson-databind (Maven) 3.1.4; jackson-annotations (openSUSE:Leap 16.0) 2.18.9-160000.1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.15.0 until 2.18.8, 2.21.4, and 3.1.4, Java Records using a PropertyNamingStrategy can bypass @JsonIgnore because POJOPropertiesCollector._removeUnwantedIgnorals() records an ignored component under its original implicit name before _renameUsing() applies the naming strategy, allowing the renamed JSON key to be assigned to the Record constructor parameter. This issue is fixed in versions 2.18.8, 2.21.4, and 3.1.4.

Published
Jul 14, 2026
Updated
Oct 24, 2026
EPSS
0.4% · 37th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-59888

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for fasterxml records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • FasterXML jackson-databind

    • >= 2.15.0, < 2.18.8, >= 2.19.0, < 2.21.4, >= 3.0.0, < 3.1.4affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavencom.fasterxml.jackson.core:jackson-databindfrom 2.15.0 · before 2.18.82.18.8
Mavencom.fasterxml.jackson.core:jackson-databindfrom 2.19.0 · before 2.21.42.21.4
Maventools.jackson.core:jackson-databindfrom 3.0.0 · before 3.1.43.1.4
openSUSE:Leap 16.0jackson-annotationsbefore 2.18.9-160000.1.12.18.9-160000.1.1
openSUSE:Leap 16.0jackson-corebefore 2.18.9-160000.1.12.18.9-160000.1.1
openSUSE:Leap 16.0jackson-databindbefore 2.18.9-160000.1.12.18.9-160000.1.1
openSUSE:Tumbleweedjackson-databindbefore 2.18.9-2.12.18.9-2.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7jackson-annotationsbefore 2.18.9-150200.3.25.12.18.9-150200.3.25.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7jackson-corebefore 2.18.9-150200.3.25.12.18.9-150200.3.25.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7jackson-databindbefore 2.18.9-150200.3.33.12.18.9-150200.3.33.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7jackson-dataformats-binarybefore 2.18.9-150200.3.24.12.18.9-150200.3.24.1
SUSE:Linux Enterprise Server 16.0jackson-annotationsbefore 2.18.9-160000.1.12.18.9-160000.1.1
SUSE:Linux Enterprise Server 16.0jackson-corebefore 2.18.9-160000.1.12.18.9-160000.1.1
SUSE:Linux Enterprise Server 16.0jackson-databindbefore 2.18.9-160000.1.12.18.9-160000.1.1

Same product

fasterxml: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-17485FasterXML jackson-databind through 2.8.10 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix…
    54Plan
  • CVE-2017-7525A deserialization flaw was discovered in the jackson-databind, versions before 2.6.7.1, 2.7.9.1 and 2.8.9, which could allow an…
    50Plan
  • CVE-2020-8840FasterXML jackson-databind 2.0.0 through 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by…
    47Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-54517Jun 23, 2026 · jackson-databind: @JsonView bypass for setterless creator properties
    21Monitor
  • ← EarlierCVE-2026-54518Jun 23, 2026 · jackson-databind: @JsonView bypass for unwrapped creator parameters in jackson-databind
    26Monitor
  • Later →CVE-2026-59889Jul 14, 2026 · jackson-databind: @JsonView ypassed for @JsonUnwrapped container properties on deserialization
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:com.fasterxml.jackson.core:jackson-databind2.18.8Package registry (OSV)
Maven:com.fasterxml.jackson.core:jackson-databind2.21.4Package registry (OSV)
Maven:tools.jackson.core:jackson-databind3.1.4Package registry (OSV)
opensuse:jackson-annotations2.18.9-160000.1.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:jackson-core2.18.9-160000.1.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:jackson-databind2.18.9-2.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:jackson-annotations2.18.9-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:jackson-core2.18.9-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:jackson-databind2.18.9-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:jackson-dataformats-binary2.18.9-150200.3.24.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-5451521 days apartjackson-databind: Case-insensitive deserialization bypasses per-property @JsonIgnoreProperties
    21Monitor
  • CVE-2026-5451621 days apartjackson-databind: Renamed @JsonIgnore'd setters can deserialize via private fields
    21Monitor

Not on record for this CVE: researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-915 · Improperly Controlled Modification of Dynamically-Determined Object Attributes

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records