# Jackson Core: Document length constraint bypass in blocking, async, and DataInput parsers

Advisory record · `GHSA-2m67-wjpj-xhg9`

- **Identifiers:** `GHSA-2m67-wjpj-xhg9`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 4 Apr 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Apr 2026, 04:17 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.1`; fixed in `3.1.1`

## Machine-written summary

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

> Jackson Core versions 3.0.0 up to but not including 3.1.1 (Maven tools.jackson.core:jackson-core) do not consistently enforce the StreamReadConstraints maxDocumentLength limit. Oversized JSON documents can be accepted without an error in blocking, async, and DataInput parsers, so an attacker sending untrusted JSON can bypass that size limit and drive up CPU and memory use. Upgrade to version 3.1.1, which is listed as the fixed version.

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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 1 Apr 2026, 21:50 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/FasterXML/jackson-core/security/advisories/GHSA-2m67-wjpj-xhg9)
- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2m67-wjpj-xhg9)

## Sources

- [GitHub Advisory Database: GHSA-2m67-wjpj-xhg9](https://github.com/advisories/GHSA-2m67-wjpj-xhg9)
- [OSV: GHSA-2m67-wjpj-xhg9](https://osv.dev/vulnerability/GHSA-2m67-wjpj-xhg9)
- <https://github.com/FasterXML/jackson-core/security/advisories/GHSA-2m67-wjpj-xhg9>
- <https://github.com/FasterXML/jackson-core/commit/74c9ee255d1534c179bc7d3de48941bf39a9079c>
- <https://github.com/FasterXML/jackson-core>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2m67-wjpj-xhg9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2m67-wjpj-xhg9/>. Everything for agents: <https://agentprime.io/llms.txt>.