How severe is GHSA-5jmj-h7xm-6q6v?

GHSA-5jmj-h7xm-6q6v has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-5jmj-h7xm-6q6v?

GHSA-5jmj-h7xm-6q6v affects the following packages: com.fasterxml.jackson.core:jackson-databind (Maven), tools.jackson.core:jackson-databind (Maven), com.fasterxml.jackson.core:jackson-databind (Maven), com.fasterxml.jackson.core:jackson-databind (Maven), com.fasterxml.jackson.core:jackson-databind (Maven). Ecosystems affected: Maven.

How do I fix GHSA-5jmj-h7xm-6q6v?

Update com.fasterxml.jackson.core:jackson-databind to 3.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5jmj-h7xm-6q6v is resolved across your whole dependency graph.

How do I detect GHSA-5jmj-h7xm-6q6v in my Maven dependencies?

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.

How do I mitigate GHSA-5jmj-h7xm-6q6v if there is no patch (or I can't update yet)?

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.

Is GHSA-5jmj-h7xm-6q6v actively exploited in the wild?

No public exploit code has been indexed for GHSA-5jmj-h7xm-6q6v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5jmj-h7xm-6q6v?

GHSA-5jmj-h7xm-6q6v has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5jmj-h7xm-6q6v?

GHSA-5jmj-h7xm-6q6v is classified as CWE-915 (CWE-915). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5jmj-h7xm-6q6v published, and has it been updated?

GHSA-5jmj-h7xm-6q6v was published on June 23, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

jackson-databind has case-insensitive deserialization bypasses per-property @JsonIgnorePropertiesGHSA-5jmj-h7xm-6q6v

MEDIUMFix: FasterXML/jackson-databind@0e1b0b2

GHSA-5jmj-h7xm-6q6v is a medium-severity (CVSS 5.3) 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-54515

Published

Jun 23, 2026

Updated

Sep 10, 2026

Affected

5 pkgs

Patched

5 / 5

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-5jmj-h7xm-6q6v.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-5jmj-h7xm-6q6v 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

5 pkgs affected

☕com.fasterxml.jackson.core:jackson-databind☕tools.jackson.core:jackson-databind☕com.fasterxml.jackson.core:jackson-databind☕com.fasterxml.jackson.core:jackson-databind☕com.fasterxml.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

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(ACCEPT_CASE_INSENSITIVE_PROPERTIES)) 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, 0e1b0b2), milestone 3.1.4. Released 2026-06-04.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.fasterxml.jackson.core:jackson-databind`	≥ 3.1.0&&< 3.1.4	3.1.4`com.fasterxml.jackson.core:jackson-databind:3.1.4`
☕Maven	`tools.jackson.core:jackson-databind`	≥ 3.1.0&&< 3.1.4	3.1.4`tools.jackson.core:jackson-databind:3.1.4`
☕Maven	`com.fasterxml.jackson.core:jackson-databind`	≥ 2.8.0&&< 2.18.9	2.18.9`com.fasterxml.jackson.core:jackson-databind:2.18.9`
☕Maven	`com.fasterxml.jackson.core:jackson-databind`	≥ 2.19.0&&< 2.21.5	2.21.5`com.fasterxml.jackson.core:jackson-databind:2.21.5`
☕Maven	`com.fasterxml.jackson.core:jackson-databind`	≥ 2.22.0&&< 2.22.1	2.22.1`com.fasterxml.jackson.core:jackson-databind:2.22.1`

Affected Products

1 product · 4 configurations

Application

jackson-databindfasterxml

≥ 3.0.0 && < 3.1.4

1 version

2.22.0

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update com.fasterxml.jackson.core:jackson-databind to 3.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5jmj-h7xm-6q6v is resolved across your whole dependency graph.
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

This is a Moderate impact flaw in jackson-databind where applications enabling case-insensitive property matching alongside per-property @JsonIgnoreProperties may inadvertently expose fields to unauthorized modification. This bypass of intended property exclusions could lead to data integrity issues within affected…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-5jmj-h7xm-6q6v (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat build of Quarkus 3.27.4.SP2	`com.fasterxml.jackson.core/jackson-databind:2.21.4.redhat-00002`	RHSA-2026:36002
Red Hat build of Quarkus 3.33.2.SP2	`com.fasterxml.jackson.core/jackson-databind:2.21.4.redhat-00002`	RHSA-2026:36013
Red Hat JBoss Enterprise Application Platform 7.4.25	`com.fasterxml.jackson.core/jackson-databind:2.18.8.redhat-00003`	RHSA-2026:67603
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7	`eap7-activemq-artemis-0:2.16.0-23.redhat_00058.1.el7eap`	RHSA-2026:67604
Red Hat JBoss Enterprise Application Platform 8.1.8.GA	`com.fasterxml.jackson.core/jackson-databind:2.18.9.redhat-00003`	RHSA-2026:70277
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 10	`eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el10eap`	RHSA-2026:70230
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8	`eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el8eap`	RHSA-2026:70228
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9	`eap8-activemq-artemis-0:2.40.0-8.redhat_00024.1.el9eap`	RHSA-2026:70229

Frequently Asked Questions

## 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(ACCEPT_CASE_INSENSITIVE_PROPERTIES)`) 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 bec

O3 Security · Impact-Aware SCA

Is GHSA-5jmj-h7xm-6q6v in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-915CWE-915

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

jackson-databind

8.0/10

Code-Review0/10

Maintained10/10

Branch-Protection3/10

Assessed Oct 19, 2026

Timeline

Disclosed

Jun 23, 2026

Last updated

Sep 10, 2026

Identifiers

GHSA-5jmj-h7xm-6q6v

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting jackson-databind are rated as high or higher (top: high).

CVE-2026-91777CVE-2026-91776CVE-2026-83557CVE-2026-68497CVE-2026-77310CVE-2026-19032CVE-2026-59888CVE-2026-59889

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026

jackson-databind has case-insensitive deserialization bypasses per-property @JsonIgnorePropertiesGHSA-5jmj-h7xm-6q6v

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Summary

Impact

Affected / Patched

Severity / CWE

Upstream fix

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is GHSA-5jmj-h7xm-6q6v in your dependencies?