jackson-databind quadratic forward-reference completion
Published 30 Sept 2026 · Updated 30 Sept 2026
Is your project on an affected com.fasterxml.jackson.core:jackson-databind?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.19.0 <2.21.7
- Fixed in
- 2.21.7
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.21.7 -DforceVersion=true- Affected
- >=3.0.0 <3.1.7
- Fixed in
- 3.1.7
mvn versions:use-dep-version -Dincludes=tools.jackson.core:jackson-databind -DdepVersion=3.1.7 -DforceVersion=true- Affected
- >=3.2.0 <3.2.3
- Fixed in
- 3.2.3
mvn versions:use-dep-version -Dincludes=tools.jackson.core:jackson-databind -DdepVersion=3.2.3 -DforceVersion=true- Affected
- >=2.5.0 <2.18.11
- Fixed in
- 2.18.11
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.18.11 -DforceVersion=true- Affected
- >=2.22.0 <2.22.3
- Fixed in
- 2.22.3
mvn versions:use-dep-version -Dincludes=com.fasterxml.jackson.core:jackson-databind -DdepVersion=2.22.3 -DforceVersion=trueDetails
Summary
When an @JsonIdentityInfo collection or map first creates N unresolved
object-ID references and later resolves the same IDs in reverse order,
jackson-databind scans the remaining pending-reference accumulator for each
resolution. A shallow JSON document whose size grows linearly can therefore
cause quadratic CPU work during deserialization.
Details
The affected path is forward-reference completion in
CollectionDeserializer.CollectionReferringAccumulator.resolveForwardReference()
and the corresponding map implementation. The implementation performs a
linear search of the pending accumulator for every resolved object ID.
The behavior is runtime-confirmed in jackson-databind 2.5.0, 2.22.1, and 3.2.1. Current 2.22 and 3.2 source branches retained the same design when rechecked. A 2.4.0 control fails closed before successful reverse-order completion, so 2.5.0 is the conservative runtime-confirmed affected floor. The patched versions are: 2.18.11, 2.21.7, 2.22.3, 3.1.7 and 3.2.3.
The vulnerable application must deserialize attacker-influenced JSON into an identity-enabled collection or map. The issue does not require deep nesting or syntactically unusual JSON.
Suggested correction: replace repeated linear lookup/removal with a keyed pending-reference structure or another design that provides linear or amortized-linear completion. A regression should preserve input order, duplicate-ID behavior, and unresolved-ID errors while bounding reverse-order resolution work.
PoC
The proof constructs a shallow collection containing N unresolved
@JsonIdentityInfo references followed by definitions of those same IDs in
reverse order. Its ID class counts equals() calls, giving a deterministic
work measure rather than a timing-dependent result.
With N=2,000, affected versions perform exactly 2,003,000 ID comparisons. An
equally sized control in which every reference is already resolved performs
zero comparisons in the pending-reference lookup path. The run is bounded to
a 512 MiB JVM. The result demonstrates quadratic growth: approximately
N * (N + 1) / 2 comparisons, plus fixed setup comparisons.
Impact
An unauthenticated source that can submit JSON to an application using the affected identity-enabled collection or map shape can consume quadratic CPU and exhaust a request-time or worker-capacity budget, causing denial of service. The application model/configuration prerequisite is material. No confidentiality, integrity, code-execution, or parser-depth impact is claimed.
Requested credit: Daniel Birtwhistle
Is GHSA-cxp5-3px4-pw24 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected com.fasterxml.jackson.core:jackson-databind, and gives you the command that fixes it.
More advisories for com.fasterxml.jackson.core:jackson-databind
- HighCVE-2026-91776jackson-databind retains every unknown raw type ID · 30 Sept 2026
- MediumCVE-2026-83557jackson-databind: Comparable missing from DefaultBaseTypeLimitingValidator's unsafe base types (incomplete PolymorphicTypeValidator denylist) · 28 Sept 2026
- HighCVE-2026-68497jackson-databind: Duration XMLGregorianCalendar Unbounded Number Parse DoS · 28 Sept 2026
- MediumCVE-2026-19032jackson-databind: Path Deserialization Missing Scheme Allowlist for FileSystemProvider Resolution · 28 Sept 2026
- MediumCVE-2026-77310jackson-databind: Incomplete fix for CVE-2026-54514: eager DNS resolution (SSRF) still present in InetAddress deserialization · 28 Sept 2026
- MediumCVE-2026-59889jackson-databind: @JsonView bypassed for @JsonUnwrapped container properties on deserialization · 21 Jul 2026
References
- Linkgithub.com/FasterXML/jackson-databind/security/advisories/GHSA-cxp5-3px4-pw24
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-91777
- Linkgithub.com/FasterXML/jackson-databind/issues/6204
- Linkgithub.com/FasterXML/jackson-databind/pull/6204
- Linkgithub.com/FasterXML/jackson-databind/commit/37ad9b81712cbb9fb62c2d2c1813593252a24b67
- Packagegithub.com/FasterXML/jackson-databind
- Linkgithub.com/FasterXML/jackson-databind/releases/tag/jackson-databind-2.18.11
- Linkgithub.com/FasterXML/jackson-databind/releases/tag/jackson-databind-2.21.7
- Linkgithub.com/FasterXML/jackson-databind/releases/tag/jackson-databind-2.22.3
- Linkgithub.com/FasterXML/jackson-databind/releases/tag/jackson-databind-3.1.7
- Linkgithub.com/FasterXML/jackson-databind/releases/tag/jackson-databind-3.2.3
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.