Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

jackson-databind: @JsonIgnore on a Record property is bypassed with a PropertyNamingStrategyGHSA-3pjw-73gf-8qr5

MEDIUMFix: FasterXML/jackson-databind#5974

GHSA-3pjw-73gf-8qr5 is a medium-severity (CVSS 6.5) CWE-915 vulnerability in com.fasterxml.jackson.core:jackson-databind. A fix is available for com.fasterxml.jackson.core:jackson-databind — see the affected versions and patch details below.

Also known asCVE-2026-59888
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3pjw-73gf-8qr5.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk
0.00%0.31%0.62%0.92%0.2%0.3%0.4%0.4%Aug 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-3pjw-73gf-8qr5 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected
☕com.fasterxml.jackson.core:jackson-databind☕com.fasterxml.jackson.core:jackson-databind☕tools.jackson.core:jackson-databind

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 (backport c7c6783)
  • 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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.fasterxml.jackson.core:jackson-databind≥ 2.15.0&&< 2.18.82.18.8com.fasterxml.jackson.core:jackson-databind:2.18.8
☕Mavencom.fasterxml.jackson.core:jackson-databind≥ 2.19.0&&< 2.21.42.21.4com.fasterxml.jackson.core:jackson-databind:2.21.4
☕Maventools.jackson.core:jackson-databind≥ 3.0.0&&< 3.1.43.1.4tools.jackson.core:jackson-databind:3.1.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.fasterxml.jackson.core:jackson-databind, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.fasterxml.jackson.core:jackson-databind to 2.18.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3pjw-73gf-8qr5 is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Moderate impact. This flaw in jackson-databind allows an attacker to bypass the @JsonIgnore annotation when deserializing Java Records that utilize a PropertyNamingStrategy. An untrusted client could exploit this to assign values to internal or privileged Record constructor parameters, potentially leading to…

ProductFixed inAdvisory
Red Hat AMQ Broker 7.13.6jackson-databindRHSA-2026:66545
Red Hat AI Inference Server 3.3rhaiis/vllm-cuda-rhel9:1789582776RHSA-2026:68699
Red Hat Enterprise Linux AI 3.3rhelai3/bootc-aws-cuda-rhel9:1790936334RHSA-2026:76041
Red Hat Enterprise Linux AI 3.3rhelai3/disk-image-cuda-rhel9:1790954179RHSA-2026:76043
Red Hat Lightspeed (formerly Insights) for Runtimes 1.0rh-lightspeed-runtimes/runtimes-agent-init-rhel9:1786378722RHSA-2026:54440
Red Hat OpenShift Dev Spaces 3.30devspaces/openvsx-rhel9:1787759145RHSA-2026:62260

Frequently Asked Questions

## 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/privile
O3 Security · Impact-Aware SCA

Is GHSA-3pjw-73gf-8qr5 in your dependencies?

Find it across Maven, including transitive dependencies.

jackson-databind: @JsonIgnore on a Record property is…