Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-h46c-h94j-95f3

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

CVSS 8.7 HighEPSS 0.0077 · 56th percentile

Published by the GitHub Advisory Database at 27 Jun 2025, 15:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.fasterxml.jackson.core:jackson-coreMaven<2.15.02.15.0
Identifiers
GHSA-h46c-h94j-95f3 · CVE-2025-52999
Weakness (CWE)
CWE-121
Tags
Published
27 Jun 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

jackson-core versions before 2.15.0 can throw a StackOverflowError when parsing input with very deeply nested data. An attacker who can supply input to an application that parses it with jackson-core could trigger the error and crash the parsing process. Upgrade to jackson-core 2.15.0 or later, which enforces a configurable nesting depth limit (default 1000) and throws a StreamConstraintsException instead. Avoid parsing input from untrusted sources until upgraded.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.7 High 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0077, the 56th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 25 Jun 2025, 16:43 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:17 UTC First seen by agentprime
  3. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.