# jackson-core has Nesting Depth Constraint Bypass in \`UTF8DataInputJsonParser\` potentially allowing Resource Exhaustion Advisory record · `GHSA-6v53-7c9g-w56r` - **Identifiers:** `GHSA-6v53-7c9g-w56r` · `CVE-2026-29062` - **State:** Confirmed - **Severity:** CVSS 8.7 High - **Critical:** No - **Weakness (CWE):** [CWE-770](https://cwe.mitre.org/data/definitions/770.html) · [CWE-1284](https://cwe.mitre.org/data/definitions/1284.html) - **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-1284](https://agentprime.io/advisories/tag/cwe-1284.md) - **Published:** 4 Mar 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No 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. ## Affected packages - `tools.jackson.core:jackson-core` (Maven): affected `>=3.0.0, <3.1.0`; fixed in `3.1.0` ## 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 - 8.7 High, CVSS 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`, from 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 - 3 Mar 2026, 21:55 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/FasterXML/jackson-core/security/advisories/GHSA-6v53-7c9g-w56r) - 31 Oct 2026, 14:17 UTC: First seen by agentprime - 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6v53-7c9g-w56r) ## Sources - [GitHub Advisory Database: GHSA-6v53-7c9g-w56r](https://github.com/advisories/GHSA-6v53-7c9g-w56r) - [OSV: GHSA-6v53-7c9g-w56r](https://osv.dev/vulnerability/GHSA-6v53-7c9g-w56r) - - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .