Advisory record · GHSA-6v53-7c9g-w56r

jackson-core has Nesting Depth Constraint Bypass in `UTF8DataInputJsonParser` potentially allowing Resource Exhaustion

CVSS 8.7 HighEPSS 0.0061 · 49th percentile

Published by the GitHub Advisory Database at 4 Mar 2026, 21:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
tools.jackson.core:jackson-coreMaven>=3.0.0, <3.1.03.1.0
Identifiers
GHSA-6v53-7c9g-w56r · CVE-2026-29062
Weakness (CWE)
CWE-770 · CWE-1284
Published
4 Mar 2026
Updated
10 Sept 2026

Machine-written summary

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

Versions 3.0.0 up to but not including 3.1.0 of jackson-core (tools.jackson.core:jackson-core) do not enforce the maxNestingDepth limit when parsing JSON from a java.io.DataInput source, and a similar gap exists in ReaderBasedJsonParser. An attacker who can supply a deeply nested JSON document to an application that parses it can trigger a StackOverflowError, causing a denial of service. Upgrade to jackson-core 3.1.0 or later; the source gives no workaround beyond avoiding untrusted input.

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.0061, the 49th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 3 Mar 2026, 21:55 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.