# CVE-2026-29062: jackson-core: Nesting Depth Constraint Bypass in `UTF8DataInputJsonParser` potentially allowing Resource Exhaustion

> Attackers can cause a Denial of Service in applications using jackson-core by supplying deeply nested JSON that bypasses nesting limits.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Mar 2026
- **Updated:** 15 Jul 2026
- **Also known as:** CLEANSTART-2026-DS38629, CLEANSTART-2026-TD10342, CLEANSTART-2026-ZD94014, ECHO-1b7a-451d-1afc, GHSA-6v53-7c9g-w56r, MINI-44wg-rqmc-mqwp, MINI-4m96-q568-8j46, MINI-4pvw-mv3q-9cgm, MINI-p696-f83h-556f, MINI-qx3p-2gc7-qx57, MINI-v362-g9x2-29wh, MINI-w2qr-96mf-xcp2, ROOT-APP-MAVEN-CVE-2026-29062, UBUNTU-CVE-2026-29062

## What is CVE-2026-29062?

CVE-2026-29062 is a high-severity denial of service vulnerability in FasterXML jackson-core, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. From version 3.0.0 to before version 3.1.0, the UTF8DataInputJsonParser, which is used when parsing from a java.io.DataInput source, bypasses the maxNestingDepth constraint (default: 500) defined in StreamReadConstraints. A similar issue was found in ReaderBasedJsonParser. This allows a user to supply a JSON document with excessive nesting, which can cause a StackOverflowError when the structure is processed, leading to a Denial of Service (DoS). This issue has been patched in version 3.1.0.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input), CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-29062?

2 open source packages ship an affected version, including tools.jackson.core:jackson-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tools.jackson.core:jackson-core` | Maven | From 3.0.0 | 3.1.0 |
| `tools.jackson.core:jackson-core` | Maven | From 3.0.0 | 3.1.0 |

Products: Fasterxml Jackson-Core.

## How do I fix CVE-2026-29062?

Upgrade tools.jackson.core:jackson-core to 3.1.0 or later.

## Is CVE-2026-29062 being exploited?

There is no known exploitation of CVE-2026-29062 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29062 and fix it if it is affected.

What it is: CVE-2026-29062 is a high-severity denial of service vulnerability in FasterXML jackson-core, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29062 in the wild and no public exploit code.

Affected packages and fixed versions:
- tools.jackson.core:jackson-core (Maven): affected from 3.0.0; fixed in 3.1.0
- tools.jackson.core:jackson-core (Maven): affected from 3.0.0; fixed in 3.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29062/ (Markdown: https://insights.sbomify.com/CVE-2026-29062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29062
- OSV: https://osv.dev/vulnerability/CVE-2026-29062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29062/
Summaries are generated and may contain mistakes; the official description above is the record.