How severe is GHSA-3wrr-7qpf-2prh?

GHSA-3wrr-7qpf-2prh has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3wrr-7qpf-2prh?

GHSA-3wrr-7qpf-2prh affects the following packages: com.fasterxml.jackson.core:jackson-databind (Maven). Ecosystems affected: Maven.

How do I fix GHSA-3wrr-7qpf-2prh?

Update com.fasterxml.jackson.core:jackson-databind to 2.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3wrr-7qpf-2prh is resolved across your whole dependency graph.

How do I detect GHSA-3wrr-7qpf-2prh 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-3wrr-7qpf-2prh if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-3wrr-7qpf-2prh actively exploited in the wild?

No public exploit code has been indexed for GHSA-3wrr-7qpf-2prh 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-3wrr-7qpf-2prh?

GHSA-3wrr-7qpf-2prh has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th 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-3wrr-7qpf-2prh?

GHSA-3wrr-7qpf-2prh is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3wrr-7qpf-2prh published, and has it been updated?

GHSA-3wrr-7qpf-2prh 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

HIGH severity

GHSA-3wrr-7qpf-2prh — jackson-databind

HIGHFix: FasterXML/jackson-databind@a1fa4ae

GHSA-3wrr-7qpf-2prh is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption 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.

jackson-databind: Deeply nested JsonNode throws StackOverflowError for toString()

Also known asCVE-2026-50193

Published

Jun 23, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 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-3wrr-7qpf-2prh.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-3wrr-7qpf-2prh by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

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

Real-World Exposure

1 pkg affected

☕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

Impact

Potential Denial-of-Service when attacker sends deeply nested JSON if (and only if) service:

Reads deeply nested (1000s of levels) JSON as JsonNode (ObjectMapper.readTree())
Writes out same (or modifided) node using JsonNode.toString()

which can consume significant amount of resources with concurrent relatively small requests (1000 nested arrays is 2kB).

Patches

Fixed in 2.14.0 via https://github.com/FasterXML/jackson-databind/issues/3447.

Workarounds

Avoid serializing JsonNode using toString(): use ObjectMapper.writeValueAsString(node)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.fasterxml.jackson.core:jackson-databind`	≥ 2.10.0&&< 2.14.0	2.14.0`com.fasterxml.jackson.core:jackson-databind:2.14.0`

Affected Products

1 product · 1 configurations

Application

jackson-databindfasterxml

≥ 2.10.0 && < 2.14.0

range

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 2.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3wrr-7qpf-2prh is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 HatImportant

This is an Important denial-of-service flaw in jackson-databind, affecting services that process deeply nested JSON data. Exploitation occurs when a service reads JSON as `JsonNode` and subsequently writes it back using `JsonNode.toString()`, leading to excessive resource consumption and potential service…

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-3wrr-7qpf-2prh (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16	`jackson-databind`	RHSA-2026:54622
Red Hat Data Grid 8.6.2	`jackson-databind`	RHSA-2026:41951
Red Hat JBoss Enterprise Application Platform 7.4.25	`com.fasterxml.jackson.core/jackson-databind:2.18.8.redhat-00003`	RHSA-2026:53806
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7	`eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el7eap`	RHSA-2026:53644
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8	`eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el8eap`	RHSA-2026:53645
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9	`eap7-activemq-artemis-0:2.16.0-22.redhat_00057.1.el9eap`	RHSA-2026:53646
Streams for Apache Kafka 3.2.1	`jackson-databind`	RHSA-2026:54435
OpenShift Developer Tools and Services 4.12	`ocp-tools-4/jenkins-rhel8:1786628667`	RHSA-2026:60247

Frequently Asked Questions

### Impact Potential Denial-of-Service when attacker sends deeply nested JSON if (and only if) service: 1. Reads deeply nested (1000s of levels) JSON as `JsonNode` (ObjectMapper.readTree()) 2. Writes out same (or modifided) node using `JsonNode.toString()` which can consume significant amount of resources with concurrent relatively small requests (1000 nested arrays is 2kB). ### Patches Fixed in 2.14.0 via https://github.com/FasterXML/jackson-databind/issues/3447. ### Workarounds Avoid serializing `JsonNode` using `toString()`: use ObjectMapper.writeValueAsString(node)