Summary
Workarounds
Users should avoid parsing input files from untrusted sources.
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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.
Frequently Asked Questions
- What is CVE-2025-52999? CVE-2025-52999 is a high-severity security vulnerability in com.fasterxml.jackson.core:jackson-core (maven), affecting versions < 2.15.0. It is fixed in 2.15.0.
- Which versions of com.fasterxml.jackson.core:jackson-core are affected by CVE-2025-52999? com.fasterxml.jackson.core:jackson-core (maven) versions < 2.15.0 is affected.
- Is there a fix for CVE-2025-52999? Yes. CVE-2025-52999 is fixed in 2.15.0. Upgrade to this version or later.
- Is CVE-2025-52999 exploitable, and should I be worried? Whether CVE-2025-52999 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-52999 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-52999? Upgrade
com.fasterxml.jackson.core:jackson-coreto 2.15.0 or later.