jackson-core can throw a StackoverflowError when processing deeply nested data

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-52999: 0.77% estimated exploitation activity in the next 30 days; percentile 55.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Workarounds Users should avoid parsing input files from untrusted sources.

Published by the source

27 Jun 2025, 15:22 UTC

Last modified by the source

27 Jun 2025, 15:22 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h46c-h94j-95f3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-52999

Advisory: jackson-core can throw a StackoverflowError when processing deeply nested data
IDs: CVE-2025-52999, GHSA-h46c-h94j-95f3
Record: https://patchnext.com/advisories/cve-2025-52999 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.fasterxml.jackson.core:jackson-core 2.15.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.fasterxml.jackson.core:jackson-core: affected < 2.15.0; fixed in 2.15.0

## Suggested inspection (read-only)
- Maven com.fasterxml.jackson.core:jackson-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.fasterxml.jackson.core:jackson-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h46c-h94j-95f3 (GitHub-reviewed advisory GHSA-h46c-h94j-95f3 lists affected ranges: Maven com.fasterxml.jackson.core:jackson-core >=0 <2.15.0)

Commands are suggestions: review each one before running it.