How severe is GHSA-h46c-h94j-95f3?

No CVSS score has been assigned to GHSA-h46c-h94j-95f3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h46c-h94j-95f3?

GHSA-h46c-h94j-95f3 affects the following packages: com.fasterxml.jackson.core:jackson-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-h46c-h94j-95f3?

Update com.fasterxml.jackson.core:jackson-core to 2.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h46c-h94j-95f3 is resolved across your whole dependency graph.

How do I detect GHSA-h46c-h94j-95f3 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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h46c-h94j-95f3 if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is GHSA-h46c-h94j-95f3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h46c-h94j-95f3 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-h46c-h94j-95f3?

GHSA-h46c-h94j-95f3 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th 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-h46c-h94j-95f3?

GHSA-h46c-h94j-95f3 is classified as CWE-121 (CWE-121). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h46c-h94j-95f3 published, and has it been updated?

GHSA-h46c-h94j-95f3 was published on June 27, 2025 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

jackson-core can throw a StackoverflowError when processing deeply nested dataGHSA-h46c-h94j-95f3

Fix: FasterXML/jackson-core#943

GHSA-h46c-h94j-95f3 is a CWE-121 vulnerability in com.fasterxml.jackson.core:jackson-core. A fix is available for com.fasterxml.jackson.core:jackson-core — see the affected versions and patch details below.

Also known asCVE-2025-52999

Published

Jun 27, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 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-h46c-h94j-95f3.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕com.fasterxml.jackson.core:jackson-core

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

jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. In versions prior to 2.15.0, if a user parses an input file and it has deeply nested data, Jackson could end up throwing a StackoverflowError if the depth is particularly large. jackson-core 2.15.0 contains a configurable limit for how deep Jackson will traverse in an input document, defaulting to an allowable depth of 1000. jackson-core will throw a StreamConstraintsException if the limit is reached. jackson-databind also benefits from this change because it uses jackson-core to parse JSON inputs. As a workaround, users should avoid parsing input files from untrusted sources.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.fasterxml.jackson.core:jackson-core`	all versions	2.15.0`com.fasterxml.jackson.core:jackson-core:2.15.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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.fasterxml.jackson.core:jackson-core to 2.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h46c-h94j-95f3 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

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

Workaround published by Red Hat

To mitigate this vulnerability, the recommendation is to avoid parsing input files from untrusted sources that may have excessively deep nested data structures; anything with a depth over 1000.

Source: Red Hat security advisory for GHSA-h46c-h94j-95f3 (CC BY 4.0)

Product	Fixed in	Advisory
OCP-Tools-4.12-RHEL-8	`jenkins-0:2.504.2.1750932984-3.el8`	RHSA-2025:10118
OCP-Tools-4.13-RHEL-8	`jenkins-0:2.504.2.1750916374-3.el8`	RHSA-2025:10119
OCP-Tools-4.14-RHEL-8	`jenkins-0:2.504.2.1750903189-3.el8`	RHSA-2025:10120
OCP-Tools-4.15-RHEL-8	`jenkins-0:2.504.2.1750856366-3.el8`	RHSA-2025:10104
OCP-Tools-4.16-RHEL-9	`jenkins-0:2.504.2.1750857144-3.el9`	RHSA-2025:10098
OCP-Tools-4.17-RHEL-9	`jenkins-0:2.504.2.1750851690-3.el9`	RHSA-2025:10097
OCP-Tools-4.18-RHEL-9	`jenkins-0:2.504.2.1750846524-3.el9`	RHSA-2025:10092
Red Hat Enterprise Linux 8	`pki-deps:10.6-8100020250731151637.489197e6`	RHSA-2025:14126

Frequently Asked Questions

### Impact With older versions of jackson-core, if you parse an input file and it has deeply nested data, Jackson could end up throwing a StackoverflowError if the depth is particularly large. ### Patches jackson-core 2.15.0 contains a configurable limit for how deep Jackson will traverse in an input document, defaulting to an allowable depth of 1000. Change is in https://github.com/FasterXML/jackson-core/pull/943. jackson-core will throw a StreamConstraintsException if the limit is reached. jackson-databind also benefits from this change because it uses jackson-core to parse JSON inputs. #